View 28330-DSH-002-A_7639755.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

data sheet 100441e october 13, 1999 cn8330 ds3/e3 framer with 52 mbps hdlc controller the cn8330 is an integral ds3/e3 framer designed to support the transmission formats defined by ansi t1.107-1988, t1.107a-1989, t1.404, and itu-t g.751 standards. all maintenance features required by bellcore tr-tsy-000009 and at&t pub 54014 are provided. in addition, the cn8330 can be optionally configured as a high-level data link controller (hdlc) usable with or without ds3/e3 framing overhead. the cn8330 provides framing recovery for m13, c-bit parity, syntran, and g.751 e3 formatted signals. a first in first out (fifo) buffer in the receive path can be enabled to reduce jitter on the incoming data. transmit and receive data is available to the host in either serial or parallel byte and nibble formats. access is provided to the terminal data link and the far end alarm/control (feac) channel, as specified in t1.107a-1989. counters are included for frame-bit errors, line code violations (lcvs), parity errors, and far end block errors (febes). two operational modes are available: microprocessor and stand-alone monitor control modes. the microprocessor control mode monitors all status conditions and provides configuration control. the stand-alone monitor mode allows the cn8330 to operate as a monitor providing status and alarm information on external pins. functional block diagram m u x source loopback unipolar conversion fifo fifo enable rxmsy cbito rxcck rxdat rxclk framing recovery overhead/ data link processing status ppdl receiver rdat[7:0] rxbck status ppdl transmitter bipolar encoder framing/ overhead insertion overhead/ data link processing line loopback txpos txneg tclko microprocessor interface ad[7:0] control txbck tdat[7:0] txcck cbiti txcki txdati txsyi to/from all blocks bypass m u x rxpos rxneg ds3cki txcki distinguishing features ? supports ds3/e3 framing modes includes high-speed hdlc controller (52 mhz) framing recovery for m13, c-bit parity, syntran, and g.751 e3 signals serial or parallel (octet or nibble) interface modes average reframe time of less than 1 ms for ds3 and less than 250 s for e3 supports the lapd terminal data link and feac channel as defined in t1.107a-1989 68-pin plcc or 80-pin mqfp surface-mount package operates from a single +5 vdc 5% power supply low-power cmos technology applications digital pcm switches digital cross-connect systems channel service units (csus) channel extenders atm switches/concentrators pbxs switched multimegabit digital service (smds) equipment test equipment routers (including hssi ports)
100441e conexant information provided by conexant systems, inc. (conexant) is believed to be accurate and reliable. however, no responsibility i s assumed by conexant for its use, nor any infringement of patents or other rights of third parties which may result from its use . no license is granted by implication or otherwise under any patent rights of conexant other than for circuitry embodied in conexan t products. conexant reserves the right to change circuitry at any time without notice. this document is subject to change withou t notice. conexant products are not designed or intended for use in life support appliances, devices, or systems where malfunction of a conexant product can reasonably be expected to result in personal injury or death. conexant customers using or selling conexant products for use in such applications do so at their own risk and agree to fully indemnify conexant for any damages resulting f rom such improper use or sale. the trademarks ?conexant? and the conexant symbol are trademarks of conexant systems, inc. product names or services listed in this publication are for identification purposes only, and may be trademarks or registered trademarks of their respective companies. all other marks mentioned herein are the property of their respective holders. ? 1999 conexant systems, inc. printed in u.s.a. all rights reserved reader response: conexant strives to produce quality documentation, and welcomes your feedback. please send comments and suggestions to conexant.tech.pubs@conexant.com . for technical questions, contact your local conexant sales office or field applications engineer. ordering information cn8330 typical ds3 application model number package ambient temperature cn8330epjd 68-pin plastic leaded chip carrier (plcc) ?40 to 85 c cn8330epd 80-pin metric quad flat pack (mqfp) ?40 to 85 c cn8331 cn8330 ds3/e3 framer tpos1 tneg1 tclk1 rline1p rline1n tline1p tline1n rxdat rxclk rxmsy rxpos rxneg ds3cki txpos txneg tclko receive serial data interface 31.6 ? 31.6 ? 0.01 37.4 ? 37.4 ? rpos1 rneg1 rclk1 rdat[7:0] rxbck txbck tdat[7:0] 8 parallel data interface (also used for hdlc payload data) tdat7 tdat6 8 (m-sync) (data) (clock) transmit serial data interface 8 ad[7:0] rd* wr* cs ale microprocessor interface txcki mon/mic*
100441e conexant i table of contents list of figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v list of tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii 1.0 product description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 1.1 pin descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 2.0 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2.1 overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2.1.1 brief block description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2.1.2 clock interface and initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 2.1.2.1 initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 2.1.3 microprocessor interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 2.1.3.1 using with specific microcontrollers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 2.1.3.2 microprocessor interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 2.1.3.3 address map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 2.2 line interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 2.2.1 transmitter line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 2.2.2 receiver line interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 2.3 transmitter operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 2.3.1 input and synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 2.3.2 ds3 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7 2.3.3 e3 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9 2.3.4 framing bit generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 2.3.5 alarm signal generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 2.3.6 terminal data link transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12 2.3.6.1 sending a message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 2.3.6.2 aborting a message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 2.3.6.3 transmitter interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 2.3.6.4 transmitter control example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 2.3.7 txfeac channel transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 2.3.8 ppdl transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 2.3.9 ppdlonly mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20 2.3.10 transmitter outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20 2.3.11 test equipment specific features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
cn8330 ds3/e3 framer with 52 mbps hdlc controller ii conexant 100441e 2.4 receiver operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 2.4.1 bipolar-to-unipolar conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 2.4.2 receive fifo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 2.4.3 received signal output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23 2.4.4 framing operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25 2.4.5 alarm detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25 2.4.6 terminal data link reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26 2.4.6.1 receiver interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28 2.4.6.2 receiver response example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28 2.4.7 rxfeac channel reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29 2.4.8 ppdl receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30 2.4.9 ppdlonly mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32 2.4.10 serial c-bit output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33 2.5 monitor mode for stand-alone operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34 2.5.1 ds3 monitor mode error outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35 3.0 registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 3.1 control registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 0x00?mode control register (cr00) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 0x01?terminal data link control register (cr01) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 0x02?status interrupt control register (cr02) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 0x03?transmit feac channel byte (cr03) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 0x04?feature control register (cr04) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 0x05?ppdl control register (cr05) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5 3.2 status registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 0x10?ds3/e3 maintenance status register (sr00) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 0x11?counter interrupt status register (sr01) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 0x12?data link interrupt status register (sr02) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 0x13?receive feac channel byte (sr03) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 0x14?terminal data link status register (sr04) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 0x15?part number/hardware version register (sr05) . . . . . . . . . . . . . . . . . . . . . . . . . 3-9 0x16?shadow status register (sr06) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10 0x20?0x26?ds3/e3 error counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 0x20?ds3 parity error counter (sr07) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 0x21?ds3 disagreement counter (sr08) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 0x22?ds3/e3 frame error counter (sr09) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 0x23?ds3 path parity error counter (sr10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12 0x24?ds3 febe event counter (sr11) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 0x25,0x26?ds3/e3 lcv counter?low and high bytes (sr12,sr13) . . . . . . . . . . . . . 3-13 3.3 memory registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14 0x30?0x37?transmit terminal data link message buffer (txtdl) . . . . . . . . . . . . . . . . 3-14 0x40?0x47?receive terminal data link message buffer (rxtdl) . . . . . . . . . . . . . . . . 3-14 3.4 register summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
cn8330 ds3/e3 framer with 52 mbps hdlc controller 100441e conexant iii 4.0 mechanical/electrical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 4.1 timing requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 4.2 environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 4.2.1 power requirements and temperature range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 4.3 electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 4.3.1 dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 4.4 mechanical specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 appendix a multimegabit hdlc formatter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-1 a.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-1 a.2 block and logic diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-3 a.3 ppdl transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-6 a.3.1 ppdl receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-7 appendix b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . b-1 b.1 ds3cki clock duty cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . b-1 b.2 overhead bit insertion in e3 parallel payload mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . b-1 b.3 hdlc formatter mode support while configured for e3 framing . . . . . . . . . . . . . . . . . . . . . . . b-2 appendix c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . c-1
cn8330 ds3/e3 framer with 52 mbps hdlc controller iv conexant 100441e
cn8330 list of figures ds3/e3 framer with 52 mbps hdlc controller 100441e conexant v list of figures figure 1-1. cn8330 pinout diagram - 68-pin plcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 figure 1-2. cn8330 pinout diagram - 80-pin mqfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 figure 1-3. cn8330 framer functional logic diagram - 68-pin plcc . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 figure 1-4. cn8330 framer functional logic diagram - 80-pin mqfp . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 figure 2-1. functional block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 figure 2-2. transmitter line driver outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 figure 2-3. clocked receiver input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6 figure 2-4. transmitter timing for serial ds3 mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 -8 figure 2-5. transmitter timing for parallel ds3 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2- 9 figure 2-6. transmitter timing for serial e3 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 -10 figure 2-7. c-bit input timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 figure 2-8. ppdl transmitter timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 figure 2-9. nibble mode with the ppdlonly control pin low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 figure 2-10. vco output signal timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 figure 2-11. receiver timing for serial ds3 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23 figure 2-12. receiver timing for parallel ds3 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 -24 figure 2-13. e3 receiver output timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 figure 2-14. ppdl receiver timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31 figure 2-15. c-bit output timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33 figure 2-16. monitor mode error indication timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 -35 figure 4-1. microprocessor interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 figure 4-2. output and input signal timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 figure 4-3. 68?pin plastic leaded chip carrier (j-bend) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 figure 4-4. 80-pin metric quad flat pack (mqfp). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 figure a-1. hdlc formatter block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .a-2 figure a-2. hdlc formatter logic diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .a-4 figure a-3. hdlc formatter logic diagram - 80-pin mqfp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-5 figure a-4. ppdl transmitter timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-6 figure a-5. ppdl receiver timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . a-9
list of figures cn8330 ds3/e3 framer with 52 mbps hdlc controller vi conexant 100441e
cn8330 list of tables ds3/e3 framer with 52 mbps hdlc controller 100nnnx conexant vii list of tables table 1-1. pin descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 table 1-2. hardware signal definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8 table 2-1. transmit encoding options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20 table 3-1. register overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15 table 3-2. status registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15 table 3-3. transmit terminal data link message buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 table 3-4. receive terminal data link message buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 table 4-1. microprocessor interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 table 4-2. clock timing requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 table 4-3. output signal timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 table 4-4. input setup/hold timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 table 4-5. absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 table 4-6. dc characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 table 4-7. output drive capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
list of tables cn8330 ds3/e3 framer with 52 mbps hdlc controller viii conexant 100nnnx
100441e conexant 1-1 1 1.0 product description the cn8330 is a frame synchronization, recovery, and signal generation circuit. applications for digital terminals include digital cross-connect systems, customer premise multiplexers, channel extenders, network managers, pbxs, switched multimegabit digital service (smds) equipment, and monitor or test equipment. the integrated circuit features a high-level data link control (hdlc) formatter usable with or without ds3/e3 framing. the cn8330 framer is designed to meet the requirements of ds3 and e3 transmission and reception formats as per ansi t1.107-1988, t1.107a-1989, t1.404, and itu-t g.751 standards. both the lapd terminal data link and the far end alarm control (feac) channel, as defined in t1.107a-1989, are supported. all maintenance features required by bellcore tr-tsy-000009 and at&t pub 54014 are furnished. hdlc data transmission according to itu-t standard q.921 and iso 3309-1984 is supported, as are smds standards prets 300 214 and tr-tsv-000773. the framer provides framing recovery for m13, c-bit parity, and g.751 e3 formatted signals. the received data stream is available serially for unchannelized applications or for external decoding of the asynchronous multiplexed formats. the framing circuit has an average reframe time of less than 1 msec for ds3 signals and less than 250 sec for e3 signals. a first in first out (fifo) buffer in the receive signal path can be enabled to reduce the jitter on the incoming data. the framer circuitry is capable of operating to 52 mhz, making it compatible with high-speed serial interface (hssi) signals or ds3 and e3 signals that are embedded in sonet sts-1 or sdh stm-1 carriers. the transmitter can process serial data from an external pin, or in byte- or nibble-oriented data format from the payload parallel data link (ppdl) data port. ds3 overhead bits or e3 frame alignment signal (fas) bits are automatically inserted. the parallel data can be formatted with idle flags, zero stuffing for transparency, and a selectable 16- or 32-bit frame check sequence (fcs). bytes or nibbles without hdlc formatting can also be transmitted. the transmitter also generates an alarm indication signal (ais), idle code, yellow alarm, and all-ones signals. ds3 c-bits (or e3 n-bits) can be inserted into the data stream from an external source. the circuit can be configured as a high-speed data formatter without inserting the cn8330 overhead bits. this allows the circuit to be used for data applications on communication links other than those requiring ds3 or e3 formatting. data bytes can be formatted with hdlc flags and fcs bytes for transmission at any speed up to 52 mhz.
1.0 product description cn8330 ds3/e3 framer with 52 mbps hdlc controller 1-2 conexant 100441e configuration, control, and monitoring of the cn8330 termination circuit and framer are accomplished with a selectable microprocessor control mode that monitors all status conditions and provides configuration control. in ds3 mode a stand-alone mode of operation is featured. this allows the circuit to operate as a monitor and provide status and alarm indications to external processing or counting circuitry including: ? ais, all-ones yellow alarm loss of signal idle code detection out-of-frame and frame-bit error counting parity error lcv (line code violation) path parity x-bit disagreement febe event counting the received ds3 c-bits (or e3 n-bits) are directed to an external pin to provide visibility for external processing, as required.
cn8330 1.0 product description ds3/e3 framer with 52 mbps hdlc controller 1.1 pin descriptions 100441e conexant 1-3 1.1 pin descriptions the cn8330 framer is packaged in a 68-pin plastic leaded chip carrier (plcc) and an 80-pin metric quad flat pack (mqfp) and shown in figure 1-1 and figure 1-2 respectively. pin assignments are listed in numerical order in table 1-1 . figure 1-3 and figure 1-4 illustrate functionally partitioned logic diagrams of the cn8330. pin descriptions, labels, and i/o assignments are detailed in table 1-2 . figure 1-1. cn8330 pinout diagram - 68-pin plcc gnd fifen vco rxpos rxneg ds3cki rxcki v dd tclko init* rxdat rxmsy rxclk rxbck/rxgapck idle/frmcar valfcs/txovh gnd 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 testi txsyo txcki txbck/txgapck tdat[7]/txsyi tdat[6]/txdati tdat[5]/txenci tdat[4]/lcverri gnd v dd tdat[3] tdat[2] tdat[1] tdat[0] txcck cbiti ppdlonly 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 cn8330 framer 9 8 7 6 5 4 3 2 1 68 67 66 65 54 63 62 61 ad[0]/los ad[1]/oof ad[2]/ais ad[3]/yel ad[4]/idle ad[5]/par ad[6]/lcv ad[7]/frmerr gnd v dd ale/paren wr*crc32 rd*/alm1 cs/alm0 dlint/sourcelb cntint/linelb mon/mic* rdat[0]/los rdat[1]/oof rdat[2]/aid rdat[3]/idle rdat[4]/frmerr rdat/lcvcar rdat[6]/rxovh rdat[7]txnrz vdd gnd cbito rxcck/txnrz txneg txpos testo sndmsg sndfcs 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
1.0 product description cn8330 1.1 pin descriptions ds3/e3 framer with 52 mbps hdlc controller 1-4 conexant 100441e figure 1-2. cn8330 pinout diagram - 80-pin mqfp cn8330 framer nc 8330_002 gnd fifen vco rxpos rxneg ds3cki rxcki v dd tclko init* rxdat rxmsy rxclk rxbck/rxgapck idle/frmcar valfcs/txovh gnd gnd nc 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 nc nc testi txsyo txcki txvbck/txgapck tdat[7]/txsyi tdat[6]/txdati tdat[5]/txenci tdat[4]/lcverri gnd gnd v dd tdat3 tdat2 tdat1 tdat0 txcck cbiti ppdlonly 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 ad0/los ad1/oof ad2/ais ad3/yel ad4/idle ad5/par ad6/lcv ad7/frmerr gnd gnd v dd ale/paren w*/crc32 rd*/alm1 cs/almo dlint/sourcelb cntint/linelb mon/mic* nc nc 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 nc rdat0/los rdat1/oof rdat2/ais rdat3/idle rdat4/frmerr rdat5/lcvcar rdat6/rxovh rdat7/txnrz v dd gnd gnd cbito rxcck/txnrz txneg txpos testo sndmsg sndfcs nc 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
cn8330 1.0 product description ds3/e3 framer with 52 mbps hdlc controller 1.1 pin descriptions 100441e conexant 1-5 table 1-1. pin descriptions pin (68-pin plcc) pin (80-pin mqfp) pin label i/o pin (68-pin plcc) pin (80-pin mqfp) pin label i/o 1 72 gnd i 35 30 v dd i 2 73 ad[7]/frmerr b/o 36 31 gnd i 3 74 ad[6]/lcv b/o 37 33 cbito o 4 75 ad[5]/par b/o 38 34 rxcck/txnrz o 5 76 ad[4]/idle b/o 39 35 txneg o 6 77 ad[3]yel b/o 40 36 txpos o 7 78 ad[2]/ais b/o 41 37 testo o 8 79 ad[1]/oof b/o 42 38 sndmsg i 9 80 ad[0]/los b/o 43 39 sndfcs i 10 2 gnd i 44 41 ppdlonly i 11 3 fifen i 45 42 cbiti i 12 4 vco o 46 43 txcck o 13 5 rxpos i 47 44 tdat[0] i 14 6 rxneg i 48 45 tdat[1] i 15 7 ds3cki i 49 46 tdat[2] i 16 8 rxcki i 50 47 tdat[3] i 17 9 v dd i5148v dd i 18 10 tclko o 52 49 gnd i 19 11 init* i 53 51 tdat[4]/lcverri i 20 12 rxdat o 54 52 tdat[5]/txenci i 21 13 rxmsy o 55 53 tdat[6]/txdati i 22 14 rxclk o 56 54 tdat[7]/txsyi i 23 15 rxbck/rxgapck o 57 55 txbck/txgapck o 24 16 idle/frmcar o 58 56 txcki i 25 17 valfcs/txovh o 59 57 txsyo o 26 18 gnd i 60 58 testi i 27 22 rdat[0]/los o 61 63 mon/mic* i 28 23 rdat[1]/oof o 62 64 cntint/linelb o/i 29 24 rdat[2]/ais o 63 65 dlint/sourcelb o/i 30 25 rdat[3]/idle o 64 66 cs/alm0 i 31 26 rdat[4]/frmerr o 65 67 rd*/alm1 i 32 27 rdat[5]/lcvcar o 66 68 wr*/crc32 i 33 28 rdat[6]/rxovh o 67 69 ale/paren i 34 29 rdat[7]/txnrz o 68 70 v dd i 1,20, 21,40, 59,60, 61,62 n/c ? 19,32, 50,71 gnd i
1.0 product description cn8330 1.1 pin descriptions ds3/e3 framer with 52 mbps hdlc controller 1-6 conexant 100441e figure 1-3. cn8330 framer functional logic diagram - 68-pin plcc rxdat rxmsy rxclk cbito rxcck/txnrz rdat[7]/txnrz rdat[6]/rxovh rdat[5]/lcvcar rdat[4]/frmerr rdat[3]/idle rdat[2]/ais rdat[1]/oof rdat[0]/los idle/frmcar valfcs/txovh vco rxbck/rxgapck txbck/txgapck txcck txpos txneg txsyo tclko txcki cbiti tdat[7]/txsyi tdat[6]/txdati tdat[5]/txenci tdat[4]/lcverri tdat[3] tdat[2] tdat[1] tdat[0] sndfcs sndmsg ppdlonly b = bidirectional, i = input, o = output receiver section transmitter section rxpos rxneg ds3cki rxcki fifen rx bipolar pos rx bipolar neg rx line clock in dejittered clock in fifo enable i i i i i i i i i i i i i i i i i i tx clock in tx c/n bit serial in tx data bit msb/tx m-sync in tx data bit 6/tx serial data in tx data bit 5/tx encoder in tx data bit 4/lcv error in tx data bit 3 tx data bit 2 tx data bit 1 tx data bit lsb send fcs send message parallel data only select ad[0]/los ad[1]/oof ad[2]/ais ad[3]/yel ad[4]/idle ad[5]/par ad[6]/lcv ad[7]/frmerr b/o b/o b/o b/o b/o b/o b/o b/o address-data 0/loss of signal address-data 1/out of frame address-data 2/alarm indication signal address-data 3/yellow alarm detect address-data 4/idle code detection address-data 5/parity error detect address-data 6/line code violation address-data 7/frame bit error test in initialization i i testi init* 13 14 15 16 11 20 21 22 37 38 34 33 32 31 30 29 28 27 24 25 12 23 57 46 40 39 59 18 60 19 9 8 7 6 5 4 3 2 ale/paren cs/alm0 rd*/alm1 wr*/crc32 mon/mic* address latch enable/parallel input enable chip select/alarm 0 read*/alarm 1 write*/cycle redundancy check 32 monitor/microprocessor* i i i i i 67 64 65 66 61 rx serial data rx m-sync rx clock rx c/n bit serial out rx c/n-bit clock out/txnrz rx data bit msb/txnrz rx data bit 6/rx overhead rx data bit 5/ line code violation carry rx data bit 4/frame bit error rx data bit 3/idle code detection rx data bit 2/alarm indication signal rx data bit 1/out of frame rx data bit lsb/loss of signal idle data rcvd/frame carry valid fcs rcvd/tx overhead voltage-controlled oscillator output rx byte clock/gapped clock tx byte clock/gapped clock tx c/n bit clock tx bipolar pos tx bipolar neg tx m-sync out tx clock out o o o o o o o o o o o o o o o o o o o o o o o testo test out 41 o cntint/linelb dlint/sourcelb 62 63 counter interrupt/line loopback data link interrupt/source loopback o/i o/i microprocessor interface 58 45 56 55 54 53 50 49 48 47 43 42 44
cn8330 1.0 product description ds3/e3 framer with 52 mbps hdlc controller 1.1 pin descriptions 100441e conexant 1-7 figure 1-4. cn8330 framer functional logic diagram - 80-pin mqfp rxdat rxmsy rxclk cbito rxcck/txnrz rdat[7]/txnrz rdat[6]/rxovh rdat[5]/lcvcar rdat[4]/frmerr rdat[3]/idle rdat[2]/ais rdat[1]/oof rdat[0]/los idle/frmcar valfcs/txovh vco rxbck/rxgapck txbck/txgapck txcck txpos txneg txsyo tclko txcki cbiti tdat[7]/txsyi tdat[6]/txdati tdat[5]/txenci tdat[4]/lcverri tdat[3] tdat[2] tdat[1] tdat[0] sndfcs sndmsg ppdlonly b = bidirectional, i = input, o = output receiver section transmitter section rxpos rxneg ds3cki rxcki fifen rx bipolar pos rx bipolar neg rx line clock in dejittered clock in fifo enable i i i i i i i i i i i i i i i i i i tx clock in tx c/n bit serial in tx data bit msb/tx m-sync in tx data bit 6/tx serial data in tx data bit 5/tx encoder in tx data bit 4/lcv error in tx data bit 3 tx data bit 2 tx data bit 1 tx data bit lsb send fcs send message parallel data only select ad[0]/los ad[1]/oof ad[2]/ais ad[3]/yel ad[4]/idle ad[5]/par ad[6]/lcv ad[7]/frmerr b/o b/o b/o b/o b/o b/o b/o b/o address-data 0/loss of signal address-data 1/out of frame address-data 2/alarm indication signal address-data 3/yellow alarm detect address-data 4/idle code detection address-data 5/parity error detect address-data 6/line code violation address-data 7/frame bit error test in initialization i i testi init* 5 6 7 8 3 12 13 14 33 34 29 28 27 26 25 24 23 22 16 17 4 15 55 43 36 35 57 10 58 11 80 79 78 77 76 75 74 73 ale/paren cs/alm0 rd*/alm1 wr*/crc32 mon/mic* address latch enable/parallel input enable chip select/alarm 0 read*/alarm 1 write*/cycle redundancy check 32 monitor/microprocessor* i i i i i 69 66 67 68 63 rx serial data rx m-sync rx clock rx c/n bit serial out rx c/n-bit clock out/txnrz rx data bit msb/txnrz rx data bit 6/rx overhead rx data bit 5/ line code violation carry rx data bit 4/frame bit error rx data bit 3/idle code detection rx data bit 2/alarm indication signal rx data bit 1/out of frame rx data bit lsb/loss of signal idle data rcvd/frame carry valid fcs rcvd/tx overhead voltage-controlled oscillator output rx byte clock/gapped clock tx byte clock/gapped clock tx c/n bit clock tx bipolar pos tx bipolar neg tx m-sync out tx clock out o o o o o o o o o o o o o o o o o o o o o o o testo test out 37 o cntint/linelb dlint/sourcelb 64 65 counter interrupt/line loopback data link interrupt/source loopback o/i o/i microprocessor interface 56 42 54 53 52 51 47 46 45 44 39 38 41
1.0 product description cn8330 1.1 pin descriptions ds3/e3 framer with 52 mbps hdlc controller 1-8 conexant 100441e table 1-2. hardware signal definitions (1 of 5) pin label signal name i/o definition microprocessor interface ale/paren address latch enable/parallel input enable i a dual-purpose active-high signal which, when mon/mic* is tied low, is microprocessor-generated and causes the cn8330 to latch in the address on the address-data bus. when mon/mic* is tied high (stand-alone mode), the parallel input for the ppdl formatter is enabled. when this pin is tied low, transmit data is sourced from the serial input tdat[6]/txdat. (1) cs/alm0 chip select/alarm 0 i a dual-purpose signal that enables read/write functions when mon/mic* is tied low, and controls ais transmission in stand-alone mode when mon/mic* is tied high. both cs and alm0 are active high signals. (1) rd*/alm1 read/alarm 1 i a dual-purpose signal that enables read data to be passed to the address-data bus when mon/mic* is tied low, and controls idle code transmission in stand-alone mode when mon/mic* is tied high, rd* is an active low signal and alm1 is active-high. (1) wr*/crc32 write/cycle redundancy check 32 i a dual-purpose signal that latches write data from the address-data bus when mon/mic* is tied low, and controls the cycle redundancy check (crc) when mon/mic* is tied high. wr* is an active low signal. in stand-alone mode, a high-speed 32-bit crc calculation is enabled if crc32 is high; if low, a 16-bit calculation is performed. (1) mon/mic* monitor/microprocessor mode select i selects either microprocessor mode when tied low, or stand-alone monitor mode when tied high. the state of mon/mic* determines which function the dual-purpose pins (ad[7:0]) serve. the standalone mode is valid only in ds3 mode. (1) ad[0]/los address-data 0/loss of signal b/o part of the bidirectional 8-bit multiplexed address-data bus when mon/mic* is tied low. when in stand-alone mode, this pin is an active-high monitor output indicating loss of signal. (1) ad[1]/oof address-data 1/out of frame b/o part of the bidirectional 8-bit multiplexed address-data bus when mon/mic* is tied low. when in stand-alone mode, this pin is an active-high monitor output indicating an out-of-frame state. (1) ad[2]/ais address-data 2/alarm indication signal b/o part of the bidirectional 8-bit multiplexed address-data bus when mon/mic* is tied low. when in stand-alone mode, this pin is an active-high monitor output indicating alarm indication signal detection. (1) ad[3]/yel address-data 3/yellow alarm detection b/o part of the bidirectional 8-bit multiplexed address-data bus when mon/mic* is tied low. when in stand-alone mode, this pin is an active-high monitor output indicating a yellow alarm. (1)
cn8330 1.0 product description ds3/e3 framer with 52 mbps hdlc controller 1.1 pin descriptions 100441e conexant 1-9 microprocessor interface ad[4]/idle address-data 4/idle code detection b/o part of the bidirectional 8-bit multiplexed address-data bus when mon/mic* is tied low. when in stand-alone mode, this pin is an active-high monitor output indicating an idle code detection. (1) ad[5]/par address-data 5/parity error detection b/o part of the bidirectional 8-bit multiplexed address-data bus when mon/mic* is tied low. when in stand-alone mode, this pin is an active-high monitor output indicating a parity error. (1) ad[6]/lcv address-data 6/line code violation b/o part of the bidirectional 8-bit multiplexed address-data bus when mon/mic* is tied low. when in stand-alone mode, this pin is an active-high monitor output indicating a line code violation. (1) ad[7]/frmerr address-data 7/ frame bit error b/o part of the bidirectional 8-bit multiplexed address-data bus when mon/mic* is tied low. when in stand-alone mode, this pin is an active-high monitor output indicating a frame bit error. (1) cntint/linelb counter interrupt/ line loopback o/i the composite interrupt signal generated by the error counters when mon/mic* is tied low. when mon/mic* is tied high, this pin controls line loopback transmission in stand-alone mode. cntint is an active-low output; linelb is an active-high input. dlint/sourcelb data link interrupt/source loopback o/i the composite interrupt signal generated by the data links when mon/mic* is tied low. when mon/mic* is tied high, this pin controls source loopback transmission in stand-alone mode. dlint is an active-low output; sourcelb is an active-high input. testi test in i used for test functions only. should be tied to ground for normal operation. init* initialization i active low initialization control. not all internal storage elements are affected by this signal. see clock interface and initialization in the overview section of the functional description chapter. testo test out o used for test functions only. should be left disconnected for normal operation. table 1-2. hardware signal definitions (2 of 5) pin label signal name i/o definition
1.0 product description cn8330 1.1 pin descriptions ds3/e3 framer with 52 mbps hdlc controller 1-10 conexant 100441e transmitter section tclko transmit clock out o used to clock out the txpos and txneg outputs. data is clocked out on the rising edge of tclko. txpos, txneg transmit bipolar positive, negative o the positive and negative pulses generated by the b3zs/hdb3 encoder. tdat[3:0] transmit data bits 3 ? 0 (bit 0 is the lsb) i in parallel mode (2) , these bits form the lower nibble of the byte-oriented data that is input to the ppdl transmitter in response to the transmit byte clock, txbck. tdat[4]/lcverri transmit data bit 4/line code violation error in i in parallel mode, the tdat[4] is bit 4 of the byte-oriented data that is input to the ppdl transmitter. in serial mode, lcverri allows test equipment to insert lcvs into the transmit stream under microprocessor control, in both ds3 and e3 modes. tdat[5]/txenci transmit data bit 5/transmit encoder in i in parallel mode, tdat[5] is bit 5 of the byte-oriented data that is input to the ppdl transmitter. in serial mode, txenci is an alternate direct input to the b3zs/hdb3 encoder. tdat[6]/txdati transmit data bit 6/transmit serial data i in parallel mode, tdat[6] is bit 6 of the byte-oriented data that is input to the ppdl transmitter. in serial mode, txdati is applied to the transmitter. tdat[7]/txsyi transmit data bit 7/transmit m-sync in i in parallel mode, tdat[7] is the msb (bit 7)of the byte-oriented data that is input to the ppdl transmitter. in serial mode, txsyi is applied to the transmitter. transmitter section txsyo transmit m-sync out o the transmit m-frame sync output. txcki transmit clock in i txcki rising edge is used to sample parallel data, while the falling edge is used to sample serial data. txbck/txgapck transmit byte clock/gapped clock o in parallel mode, txbck clocks the byte-oriented data that is input to the ppdl transmitter. in serial mode, txgapck is a transmit clock that is gapped during overhead bit intervals in either e3 or ds3 modes. sndmsg send message i in parallel mode, sndmsg initiates message transmission in the ppdl transmitter. sndfcs send frame check sequence i in parallel mode, sndfcs initiates transmission of the 16- or 32-bit frame check sequence on the ppdc transmitter. cbiti transmit c/n-bit serial in i the serial c-bit (ds3 mode) or n-bit (e3 mode) data input to be transmitted. txcck transmit c/n-bit clock o used to sample the cbiti input on the falling edge of txcck. ppdlonly payload parallel data only select i enables the ppdl-only mode in which no ds3/e3 framing is inserted. this mode is entered by tying this pin high. table 1-2. hardware signal definitions (3 of 5) pin label signal name i/o definition
cn8330 1.0 product description ds3/e3 framer with 52 mbps hdlc controller 1.1 pin descriptions 100441e conexant 1-11 receiver section ds3cki ds3 receive line clock in i clock input ds3cki should be connected to a 44.736 mhz source (34.368 mhz for the e3) derived from incoming receive data. rxpos, rxneg receive bipolar positive/negative i the input positive and negative pulses are sampled on the rising edge of the receiver input clock (ds3cki) and should be a full clock period wide. rxcki receive dejittered clock in i used to read the received data out of the internal fifo (required only if fifo is enabled). if unused, tie to ground. fifen fifo enable i an active-high input which enables the internal fifo, used to dejitter the received data by using the dejittered clock input, rxcki. when fifen is low, the fifo is bypassed and the serial data is output with respect to the incoming clock, ds3cki. rxdat receive serial data o rxdat is the serial data bit stream clocked out on the rising edge of rxclk. rxmsy receive m-sync o the m-frame synchronization output recovered from the incoming serial data stream. rxclk receive clock o the receive clock used internally to clock out the serial data stream onto rxdat. rxbck/rxgapck receive byte/gapped clock o when in serial mode, rxgapck provides a gapped clock signal during every overhead bit (in both ds3 and e3 modes). in parallel mode, rxbck is used to internally clock out the receive byte-oriented data on rdat[7:0]. cbito receive c/n-bit serial out o the receive serial c-bit (ds3 mode) or n-bit (e3 mode) data. cbito changes on the rising edge of rxcck. rxcck/txnrz receive c/n-bit clock out/transmit nrz o a clock that indicates transitions in the cbit0 signal. in ppdl-only mode, transmit nrz data is available on this pin. rdat[0]/los receive data byte 0/loss of signal o part of the 8-bit data bus output from the ppdl receiver when parallel mode is enabled. when parallel mode is disabled, this pin is an active-high monitor output indicating loss of signal. rdat[1]/oof receive data byte 1/ out of frame o part of the 8-bit data bus output from the ppdl receiver when parallel mode is enabled. when parallel mode is disabled, this pin is an active-high monitor output indicating out-of-frame. rdat[2]/ais receive data byte 2/alarm indication signal o part of the 8-bit data bus output from the ppdl receiver when parallel mode is enabled. when parallel mode is disabled, this pin is an active-high monitor output indicating alarm indication signal. table 1-2. hardware signal definitions (4 of 5) pin label signal name i/o definition
1.0 product description cn8330 1.1 pin descriptions ds3/e3 framer with 52 mbps hdlc controller 1-12 conexant 100441e receiver section rdat[3]/idle receive data byte 3/idle code detection o part of the 8-bit data bus output from the ppdl receiver when parallel mode is enabled. when parallel mode is disabled, this pin is an active-high monitor output indicating idle code detection. rdat[4]/ frmerr receive data byte 4/frame error detection o part of the 8-bit data bus output from the ppdl receiver when parallel mode is enabled. when parallel mode is disabled, this pin is an active-high monitor output indicating frame error detection. rdat[5]/ lcvcar receive data byte 5/line code violation carry o part of the 8-bit data bus output from the ppdl receiver when parallel mode is enabled. when parallel mode is disabled, this pin is an active-high ripple carry output from the lcv error counter. rdat[6]/rxovh receive data byte 6/receive overhead detection o part of the 8-bit data bus output from the ppdl receiver when parallel mode is enabled. when parallel mode is disabled, this pin is an active-low monitor output indicating the receive overhead bit positions. rdat[7]/txnrz receive data byte 7/ trans- mit nrz out o part of the 8-bit data bus output from the ppdl receiver when parallel mode is enabled. when parallel mode is disabled, this pin is a monitor output for the transmit nrz data. idle/ frmcar idle/frame carry o set if an idle flag is received after a non-idle sequence, when parallel mode is enabled. when parallel mode is disabled, this pin is an active-high ripple carry output from the frame error counter. valfcs/txovh valid fcs received/transmit overhead o active high if a valid fcs was received, when parallel mode is enabled. when parallel mode is disabled, this pin is an active-low transmit overhead bit position indicator. vco voltage-controlled oscillator output o used as the phase control for the clock recovery circuit that generates the dejittered clock, rxcki. valid only when fifen is high. fifen enables the internal fifo when tied high. vcc and gnd v dd supply voltage four pins are provided for power. gnd ground five pins are provided for ground. not connected nc not connected these pins are not connected internally. note(s): (1) standalone operation is valid only in ds3 mode. (2) parallel mode is enabled by setting the parallel data enable bit [paraen;cr04.3] in the feature control register [cr04; 0x04] when mon/mic* is low. when mon/mic* is high, parallel mode is entered by tying the ale/paren pin high. table 1-2. hardware signal definitions (5 of 5) pin label signal name i/o definition
100441e conexant 2-1 2 2.0 functional description 2.1 overview 2.1.1 brief block description a block diagram of the circuit is illustrated in figure 2-1 . the receive b3zs/hdb3 signal is decoded and the bipolar input is converted to a unipolar, clocked serial data stream. frame bit content is checked and the overhead bit data links and alarms are extracted. the receive clock is provided at the receiver output (rxclk). the data is also connected to a payload parallel data link (ppdl) receiver that decodes message blocks using the high-level data link control (hdlc) format (refer to appendix a in this document for a description of the hdlc formatter). the recovered data bytes are provided on a parallel output port with a byte clock. the ppdl receiver can also be programmed to operate in nibble mode or transparently without hdlc formatting. a first in first out (fifo) memory buffer in the receive signal path can be enabled to reduce the jitter on the incoming data. the receive data is clocked into the fifo buffer after bipolar decoding. the fifo buffer provides a voltage controlled oscillator (vco) control signal to an external clock recovery circuit. a dejittered clock (rxcki) from the vco is then used to read the data from the fifo buffer to the remaining receiver circuitry. the transmitter is capable of sending either serial data from an external pin, or byte- or nibble-oriented data from the ppdl data port. ds3 overhead bits or e3 frame alignment signal (fas) bits are automatically inserted. parallel data can be formatted with idle flags, zero stuffing for transparency, and a selectable 16- or 32-bit frame check sequence (fcs). bytes or nibbles without hdlc formatting can also be transmitted. the transmitter is able to send ais, idle code, yellow alarm, and all-ones signals. ds3 c-bits (or e3 n-bits) can be optionally inserted into the data stream from an external source. lapd (link access procedure-d) receiver and transmitter circuitry is provided for the terminal data link in ds3 c-bit parity format and the e3 mode. in c-bit mode, the three c-bits in subframe 5 of the m-frame are used for the terminal data link. in e3 mode, the n-bit is used for the terminal data link. the microprocessor interface or external outputs monitors all status indications in the received signal. for both ds3 and e3 modes, indications include ais, all-ones, and yellow alarm detection; and out-of-frame (oof) and frame bit error counting. in addition, loss of signal, idle code, and parity error detection; line code violation (lcv), path parity, and febe event counting; and parity and x-bit disagreement counting are provided for ds3 mode. the received ds3 c-bits (or e3 n-bits) are available on an external pin to provide visibility for external processing, if necessary.
2.0 functional description cn8330 2.1 overview ds3/e3 framer with 52 mbps hdlc controller 2-2 conexant 100441e figure 2-1. functional block diagram unipolar conversion fifo buffer mux rxpos rxneg ds3cki txpos txneg txcki sourcelb rxcki fifen rx timing receive clock and data control interrupts address/data microprocessor interface control status receive ppdl transmitter los, lcv vco rxdat, rxclk rxbck rdat[7:0] status: idle valfcs receive byte message buffer status: oof frame error parity path parity febe x bit format rxmsy gapped clock cbito,rxcck status: ais idle txbck tdat[7:0] sndmsg, sndfcs cbiti txcck txsyo framing and overhead bit insertion txnrz data mux bipolar encoding fifo data for line loopback txpos txneg tclko txenci linelb feac channel terminal data link generator payload bit pattern insert febe generation txdati txcki txsyi transmit test equipment feature select ppdl receiver feac channel frame recovery frame/ overhead bit check terminal data link receiver payload bit check transmit byte message buffer data clk mux rxpos rxneg ds3cki linelb
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.1 overview 100441e conexant 2-3 2.1.2 clock interface and initialization the cn8330 clock input (txcki) controls the transmitter. this input should be supplied with a 44.736 mhz clock in ds3 mode and a 34.368 mhz clock in e3 mode. tdat[6]/txdati is sampled on the falling edge of txcki and tdat[7]/txsyi is sampled on the rising edge of txcki. the transmit pulses txpos and txneg are clocked out on the rising edge of tclko. ds3cki is the raw data clock that accompanies the rxpos and rxneg data pulse inputs for the receiver. if the fifo buffer is enabled, the data is clocked into the fifo buffer after b3zs/hdb3 decoding. rxcki is the dejittered version of ds3cki and is used to clock the receive data out of the fifo buffer (if enabled) to the rest of the receiver circuitry. if the fifo buffer is disabled, ds3cki clocks the data into all of the receiver circuitry and the rxcki input should be grounded. clock timing requirements are given in the electrical and mechanical specifications chapter. 2.1.2.1 initialization the cn8330 can be initialized with an active-low input pulse of at least 200 ns duration on the init* pin. all error counters are initialized to zero when this input is active low if the transmit and receive clocks are present. initialization is not required for proper operation. during initialization (active low) host cannot read or write any cn8330. 2.1.3 microprocessor interface the cn8330 can be controlled by a microprocessor or a microcontroller through an 8-bit multiplexed address/data interface. an interface to an intel 8051 family processor or equivalent, or motorola 68hc11 family or equivalent is provided. the microprocessor interface is enabled by tying the mon/mic* pin low. the cn8330 is connected to the microprocessor exactly like static ram. 2.1.3.1 using with specific microcontrollers the microprocessor interface is designed to allow direct connection of intel 8051 family, motorola 68hc11 family, or equivalent microcontrollers. the controller interface to the cn8330 consists of 14 pins: address latch enable (ale), read enable (rd*), write enable (wr*), chip select (cs), eight multiplexed address/data bits (ad[7:0]), and two interrupts (dlint/sourcelb and cntint/linelb). if a 68hc11 controller is used, then its address strobe as is connected to ale, enable is connected to rd*, and read/write* (r/w*) is connected to wr*. the chip select input (cs/alm0) allows the control of multiple ics from a single microprocessor. interrupt outputs are used for data link and maintenance operations and provide active-low interrupts.
2.0 functional description cn8330 2.1 overview ds3/e3 framer with 52 mbps hdlc controller 2-4 conexant 100441e 2.1.3.2 microprocessor interrupts there are two separate interrupt pins that can be connected to the microprocessor (or microcontroller): counter and data link. the counter interrupt pin (cntint/linelb) combines seven sources of interrupts on an external pin connected to the microprocessor. this interrupt signal is active low and is a composite indication of all interrupt sources that are enabled in the status interrupt control register [cr02;0x02]. the interrupt source can be determined by reading the counter interrupt status register [sr01;0x11]. the data link interrupt pin (dlint/sourcelb) is a composite indication of the interrupts from four sources. the interrupt source can be determined by reading the data link interrupt status register [sr02;0x12]. when the c-bit parity mode/enable dlint bit [cbitp/dl;cr00.0] is not set, the dlint/sourcelb pin is held high (inactive). the two interrupt pins are open-drain outputs and can be connected to form a single-wire ored interrupt, if desired. 2.1.3.3 address map the register address map for the cn8330 is given in table 3-1 through table 3-4, register summary. there are three types of registers: control registers, which can be read or written; status registers and counters which can only be read; and data link message buffers which can be read or written. the control registers serve as latches that are modified by a microprocessor write operation and can also be read to verify contents. they are located at addresses 0x00 ? 0x05. status registers are located at addresses 0x10 ? 0x16. maintenance error counters are located at addresses 0x20 ? 0x26. the transmit terminal data link message buffers are located at addresses 0x30 ? 0x37, and the receive terminal data link message buffers are located at addresses 0x40 ? 0x47. the chip select input (cs/alm0) must be high to address the cn8330 and to enable read or write operations.
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.2 line interfaces 100441e conexant 2-5 2.2 line interfaces 2.2.1 transmitter line interface the transmitted line signals are shown in figure 2-2 . nine bits of a representative output sequence are shown. separate signal pins provide the appropriate output signal for positive and negative pulses. the outputs are a full clock period wide and change on positive clock transitions of the tclko pin. for additional information on the txpos and txneg outputs refer to transmitter outputs in the transmitter operation section in this chapter b3zs/hdb3 encoding is performed automatically on the output data stream; however, this encoding can be disabled to send ami data without any zero code suppression. transmit nrz data, prior to b3zs/hdb3 encoding, is also available on the rdat[7]/txnrz pin when parallel mode is not selected and on the rxcck/txnrz pin when ppdlonly mode is selected. figure 2-2. transmitter line driver outputs tclko txpos txneg
2.0 functional description cn8330 2.2 line interfaces ds3/e3 framer with 52 mbps hdlc controller 2-6 conexant 100441e 2.2.2 receiver line interface the line interface for the receive bipolar signals consists of two logic-level signals that represent the positive and negative bipolar line pulses (rxpos, rxneg) and an input (ds3cki) for an externally derived clock at a nominal frequency of 44.736 mhz or 34.368 mhz. the receiver line signals are shown in figure 2-3 . nine bits of a representative input sequence are shown. the input signal is sampled on the rising edge of the clock signal. b3zs/hdb3 decoding is provided internally. decoding can be defeated for nrz inputs by connecting the nrz data input to both the rxpos and rxneg inputs or by selecting the ami mode/lcv type 2 bit [ami/lcv2;cr04.6] in the feature control register [cr04;0x04]. figure 2-3. clocked receiver input ds3cki rxpos rxneg
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.3 transmitter operation 100441e conexant 2-7 2.3 transmitter operation the transmitter circuit is synchronized to the transmit input data by an external synchronization signal. the external synchronization signal sets the m-frame reference for transmitted signals. 2.3.1 input and synchronization the input to the transmitter consists of the transmit serial data input (or the ppdl transmitter data), transmit clock, and transmit m-frame sync signal. an m-frame sync signal output is available on the txsyo pin to synchronize external circuitry, if desired. if an input sync is not provided, the cn8330 generates a sync internally whose position is indicated by txsyo. in this case, the sync input should be grounded. the tdat[7]/txsyi is sampled on the rising edge of txcki and tdat[6]/txdati is sampled by the falling edge of txcki. 2.3.2 ds3 mode the input bits are synchronized to the m-frame sync signal, which can either be externally provided or taken from the m-frame sync signal that is internally generated. serial input data on tdat[6]/txdati must contain bit positions for the overhead bits, although these are not used unless external insertion is enabled. the clock frequency is nominally 44.736 mhz and the transmit data input is sampled on the falling edge of the clock signal. the path delay of the transmitter from the serial data input to the positive and negative outputs is six cycles of the transmit clock. this delay includes b3zs/hdb3 coding. the delay from the serial data input to the nrz output is two clock cycles and the coding delay of the b3zs encoder is four clock cycles.
2.0 functional description cn8330 2.3 transmitter operation ds3/e3 framer with 52 mbps hdlc controller 2-8 conexant 100441e if the tdat[7]/txsyi m-frame sync signal is provided, it is sampled on the rising edge of txcki and should have a low-to-high transition from the last bit of the m-frame (bit 680 of subframe 7) to the x1 bit (bit 1 of subframe 1). txsyo is clocked out by the rising edge of txcki and may be used for synchronization of external circuitry. serial data may alternatively be provided in response to the txbck/txgapck pin without the need for providing frame synchronization or overhead bit slots. the gapped clock output is a gated version of txcki with one pulse gapped for each overhead bit position (one pulse every 85 clock cycles). a transmit overhead valfcs/txovh bit position indicator pulse is available when the ppdl is not selected. this pulse is clocked out on the falling edge of txcki and may be of use for providing overhead bits externally. a timing diagram is presented in figure 2-4 with propagation delays shown as negligible. refer to the electrical and mechanical specifications chapter for actual propagation delay specifications. figure 2-5 illustrates the transmitter timing for the parallel ds3 mode. this mode is enabled by setting the parallel data enable bit [paraen;cr04.3] in the feature control register and setting the disable ppdl transparency bit [disppdl;cr05.1] in the ppdl control register [cr05;0x05]. the sndmsg pin should be tied high and the sndfcs tied low to ensure that flags or fcs bytes are not transmitted. figure 2-4. transmitter timing for serial ds3 mode txcki valfcs/ txovh txbck/ txgapck txsyo tdat[6]/txdati (serial in) tdat[7]/txsyi (sync in) subframe 1 84 info bits x1 84 info bits subframe 7 f4 low during subframe 7
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.3 transmitter operation 100441e conexant 2-9 2.3.3 e3 mode the clock and data edges for e3 mode have the same relationship as in ds3 mode. the synchronization overhead for e3 mode is 12 contiguous bits in each frame rather than being distributed throughout the frame. the input bits are synchronized to the m-frame sync signal, which can be externally provided or internally generated from the m-frame sync signal. serial input data must contain bit positions for the overhead bits, although these are not used unless external insertion is enabled. the clock frequency is nominally 34.368 mhz and the transmit data input is sampled on the falling edge of the clock signal. the path delay of the transmitter from the serial data input to the positive and negative line driver outputs is seven cycles of the transmit clock. this delay includes hdb3 encoding. the delay from the serial data input to the nrz output is two clock cycles and the coding delay of the hdb3 encoder is five clock cycles. the tdat[7]/txsyi signal should have a low-to-high transition from the last bit of the m-frame (bit 1536) to the first bit of the fas (bit 1). txsyo may be used to synchronize external circuitry. serial data may be provided alternatively in response to the txbck/txgapck output without providing frame synchronization or overhead bit slots. figure 2-6 illustrates the timing with propagation delays shown as negligible. refer to the electrical and mechanical specifications chapter for actual propagation delay specifications. note that in e3 mode gapped clock txbck/txgapck is one clock cycle late relative to the overhead bit positions when compared to the same relationship in ds3 mode. this clock can still be used for data input to the transmitter. the last data bit clocked in external circuitry by the gapped clock output should be held during the overhead interval and will be sampled by the first falling edge of txcki after the overhead interval. this bit will appear as the first bit in the information field after the overhead field. figure 2-5. transmitter timing for parallel ds3 mode data data data data data subframe 7 subframe 1 txcki txsyo txbck/ txgapck tdat[7:0]
2.0 functional description cn8330 2.3 transmitter operation ds3/e3 framer with 52 mbps hdlc controller 2-10 conexant 100441e 2.3.4 framing bit generation in ds3 mode, all f and m framing bits are automatically generated by the transmitter circuitry. additionally, the transmitter calculates the parity of each m-frame and inserts this data into bits p1 and p2 of the following m-frame. bits x1 and x2 contain ones unless the transmit alarm control 0 bit [txalm0; cr00.4] in the mode control register [cr00;0x00] is set. if set, bits x1 and x2 contain zeros. if c-bit parity mode is selected, all c-bit positions are generated automatically by the transmitter if the external c-bit insert bit [extcbit;cr00.2] is low. if high, all c-bits are generated internally except for the cp (subframe 3) an febe (subframe 4) bit positions. these bits must be provided on the cbiti pin at the proper time in response to txcck as shown in figure 2-7 . the cbiti data must be valid on the falling edge of txcck. this allows the chip to be used in a repeater mode with pass-through of the path parity and febe information. if c-bit parity mode is not selected, all c-bit positions come from either the serial data stream or the cbiti pin depending on the extcbit setting in the mode control register. the x, p, m, and f bit positions may be inserted from the transmit serial data stream by setting external overhead insert bit [extovh;cr00.3] high. figure 2-6. transmitter timing for serial e3 mode txcki valfcs/ txovh txbck/ txgapck txsyo tdat[6]/txdati (serial in) tdat[7]/txsyi (sync in) a/n/1100 1520/1524 info bits low for 12 bits (fas,a,n) info high for 12 bits (fas,a,n) 10-bit fas
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.3 transmitter operation 100441e conexant 2-11 in e3 mode, the fas pattern is automatically generated by the transmitter circuitry. the transmitter also inserts the a-bit as determined from the transmit alarm control 1 bit [txalm1;cr00.5] and the n-bit from the terminal data link circuitry. if extcbit is high, the n-bit must be provided on the cbiti pin in response to the rising edge of txcck. the txovh/valfcs and txsyo signals are active during the 12 bits of overhead. if the ppdl is enabled, the transmitter also inserts a 1100 pattern after the normal 12-bit framing sequence for a total of 16 overhead bits. this 16-bit pattern is for conformance with draft standard prets 300 214 for smds applications. in this mode, the valfcs/txovh and txsyo signals are active during all 16 bits of overhead. all overhead bits can be inserted via the serial data input by setting the extovh bit high. 2.3.5 alarm signal generation three alarm signals, yellow, ais, and idle, can be generated by the transmitter in ds3 mode by setting the txalm[1,0] bit pair in the mode control register. the yellow alarm is contained in the x1 and x2 bits. the x1 and x2 bits are normally set to 1. the yellow alarm (x1 and x2 bits = 0) can be sent by setting the txalm bit pair to 01. the ais signal is enabled by setting the bit pair to 11. the ais signal has valid framing and parity, all c-bits set to zero regardless of framing mode, both x-bits set to one, and the payload set to a 1010... pattern starting with 10 after each overhead bit. the idle code signal is enabled by setting the bit pair to 10. the idle code signal has valid framing and parity, both x-bits set to one, and the payload set to a 1100... pattern starting with 11 after each overhead bit. if the framing mode is m13, all c-bits are set to zero during transmission of the idle signal. if the framing mode is c-bit parity, the c-bits in subframe 3 are set to zero, and the other c-bits are from the selected source. this allows full use of the terminal data link and transmit feac channel during transmission of idle code. figure 2-7. c-bit input timing txcck cbiti subframe 1 subframe 7 subframe 2 subframe 6 c1 c2 c3 c1 c2 c3 c1 c2 c3 c1 c2 c3
2.0 functional description cn8330 2.3 transmitter operation ds3/e3 framer with 52 mbps hdlc controller 2-12 conexant 100441e in c-bit parity mode with internal sourcing of the c-bits, febe alarms are generated automatically in the transmitter when the receiver detects either a frame bit error or a c-bit parity error in an m-frame. the 3-bit febe pattern that is transmitted is contained in the febe pattern bit field [febec[3:1];cr04.2:0] of the feature control register. bit 2 is placed in the c1 position of subframe 4 during the alarm condition, bit 1 is placed in the c2 position, and bit 0 is placed in the c3 position. when no alarm condition is present, the febe channel contains all ones. therefore, to prevent disabling proper febe operation, the febe field should be written to any combination other than 111. an unframed, all-ones signal can be transmitted by setting both txalm0 and txalm1 to a 1 and extovh cleared to a 0. in e3 mode, the ais (unframed all-ones) is enabled by setting txalm0 high. the yellow alarm is enabled by setting txalm1 high. this causes the transmitted a-bit to be set to a one. 2.3.6 terminal data link transmitter the terminal data link transmitter consists of the three c-bits in subframe 5 of the m-frame in ds3 mode or the n-bit in e3 mode and uses the lapd protocol. when the send message bit [txmsg;cr01.0] of the terminal data link control register [cr01;0x01] is low, the data link transmitter is continuously sending idle flags (01111110). when high, message transmission is initiated. transmission of the fcs bytes is controlled by the send frame check sequence bit [txfcs;cr01.1]. if a nonstandard fcs is required, it may be loaded into the message buffer and transmitted as part of the message. a message in progress may be abandoned by setting the abort message bit [txabort;cr01.2]. this will cause an abort flag (11111110) to be transmitted, followed by idle flags, until the send message bit is reactivated. two consecutive messages may share ending and beginning idle flags. the transmitter can be disabled by setting the disable terminal data link transmission bit [distxtdl;cr01.6] to a one. this causes all ones to be sent in the data link bit positions. the terminal data link transmitter is under control of the c-bit parity mode/enable dlint/sourcelb (cbitp/dl;cr00.0), e3 framing mode [e3frm;cr00.1], external c-bit insert, and transmit alarm control bits in the mode control register. in the terminal data link control register, the transmitter is under the control of the txmsg, txfcs, txabort, send byte [txbyte[2:0];cr01.5:3], and distxtdl bits. an interrupt for use with data link operations is available on the dlint/sourcelb output pin and status bits for determining the interrupt source are located in the data link interrupt status register [sr02;0x12]. the framer mode must be set to either c-bit parity mode or e3 mode for terminal data link transmission to take place. in c-bit parity mode, the three c-bits in subframe 5 of the m-frame will be used for transmission. in e3 mode, the n-bit will be used for transmission. when e3 mode is selected, the cbitp/dl bit must also be set to enable interrupts on the dlint/sourcelb pin. if neither mode is set, terminal data link transmission will not take place. if the extcbit bit is set in e3 mode, terminal data link transmission will be disabled. in c-bit parity mode, extcbit has no effect on terminal data link transmission. setting the transmit alarm control [1,0] bits for transmission of ais or all ones in either c-bit parity mode or e3 mode will disable transmission of the terminal data link. transmission of yellow alarms or idle codes has no effect on terminal data link transmission.
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.3 transmitter operation 100441e conexant 2-13 if the framer is in a mode that allows data link transmission as described previously, then the terminal data link control register is the main control register used for transmit data link operations. the distxtdl bit must be set low to enable operation of the data link. if high, an all-ones signal will be transmitted in the data link bit positions in the outgoing serial stream. with the data link enabled, the txmsg, txfcs, and txabort bits control operation. the txbyte[2:0] bits form a pointer to the transmit terminal data link message buffer [txtdl;0x30 ? 0x37] used by the data link transmitter. the transmitter implements an lapd data link per ccitt standard q.921. the functions provided by the data link transmitter circuitry are transparency zero stuffing, fcs generation, idle flag generation, and abort flag generation. the total length of the message has no restrictions. q.921 requires all messages be integral numbers of 8-bit bytes. the transmitter can only transmit 8-bit bytes. byte transmission time for the transmitter is approximately 284 microseconds in c-bit parity mode and approximately 357 microseconds in e3 mode. the transmit terminal data link message buffer is an 8-byte buffer provided for the transmit data link channel to minimize processor interruptions. filling of this buffer is accomplished by the processor in the same manner as writes to control registers. this buffer can be read as well as written to verify contents. the buffer is divided into two halves to reduce the real-time requirements on the processor. the processor loads four bytes at a time, while the data link transmitter reads from the other half of the buffer. this gives the processor at least 1 msec to assemble the next four bytes of message for transmission before the next interrupt is issued. interrupts are issued each time the transmitter circuitry reaches a 4-byte buffer boundary. the transmitter must initialized with bits 0 through 6 of the terminal data link control register written to zero. this will enable the transmitter to send idle flags on the data link. no interrupts are generated when the data link is sending idle flags, thus no processor intervention is required until a message is to be sent. 2.3.6.1 sending a message beginning with an idle channel, the processor writes the first four bytes of message data to the transmit terminal data link message buffer. the first byte of data to be transmitted should be written to address 0x30. the message is read from the buffer in ascending order starting at address 0x30 and ending at address 0x37. the least significant bit (lsb) in each byte is the first transmitted. this buffer may be written well before the message is to be sent, if desired. after the first block of data is present in the buffer memory, the processor writes to the terminal data link control register to begin transmission (txmsg = 1, txbyte[2:0] = 011, txfcs = 0, txabort = 0). the 3-bit txbyte[2:0] field is functionally split into two parts. the most significant bit (msb) indicates to the transmitter circuitry which half of the buffer to read from next. the two lsbs indicate the stop location, i.e., where the last message byte is located. when the new controls are latched by the transmitter circuitry, the processor will be interrupted for the next set of controls. now, the processor has up to 1 msec to write a new set of controls to the control register. the processor may now also write the next block of data to the next half of the message buffer. when the end of a message is reached, or in the event of a short message, there may not be exactly 4 bytes remaining. in this case, the processor writes the remaining data to the message buffer as usual. the processor now must write the highest location used to the txbyte[2:0] field. also, the txfcs bit is set to 1. this causes the fcs to be sent after this last block of data.
2.0 functional description cn8330 2.3 transmitter operation ds3/e3 framer with 52 mbps hdlc controller 2-14 conexant 100441e when this set of controls is latched, the processor will be interrupted. at this time, a new message may be sent, or the txmsg bit may be set to zero to send idle flags. if a new message is to be sent immediately, the next half of the transmit buffer can be written, and the terminal data link control register optioned accordingly. this will result in only one idle flag being transmitted between messages. if there is no new message ready, the processor must write txmsg to zero. if this is not done within 1 msec, undefined data will be transmitted. 2.3.6.2 aborting a message to abort a message in progress, the controller writes the txabort bit to one in the terminal data link control register. the transmitter will finish sending the message byte in progress, then transmit an abort flag (11111110). after writing the abort signal to the control register, a second write may follow immediately to cause the transmitter to go to the idle condition, or to transmit another message. in the latter case, the abort flag will be followed by one idle flag, and then the new message will begin. if the second write is not performed, the formatter will continue to transmit abort flags until instructed otherwise. 2.3.6.3 transmitter interrupts the transmitter generates an interrupt when it has latched the present set of controls and is ready for a new set. there will not be any interrupts during the transmission of idle flags. therefore, to start a message from an idle condition, the first half of the buffer and the proper control bits are written by the processor. when the circuit latches these controls internally, an interrupt will immediately be issued for the next set of control bits. the processor then has up to 1 msec (4 byte periods) to respond to the interrupt. the data link interrupt status register [sr02;0x12] indicates the source of the interrupt but not the cause. the controller software must know from message context what response is required. the interrupt is an active low level, not a pulse. the interrupt will be cleared upon the writing of the terminal data link control register. a write operation must be performed to clear the current interrupt and prevent missing later interrupts. if the interrupt is a mid-message interrupt, a new data link control word must be written, with bytes equal to the ending location of the next message block. the msb of txbyte[2:0] will inform the transmit circuitry which half of the buffer to read next. interrupts from the terminal data link transmitter will appear in the transmit terminal data link interrupt bit [txtdlitr;sr02.3]. interrupts must be enabled to appear on dlint/sourcelb by setting the cbitp/dl bit to a 1 in the mode control register in either c-bit parity or e3 mode.
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.3 transmitter operation 100441e conexant 2-15 2.3.6.4 transmitter control example this example will show the sequence necessary to transmit a 10-byte hex message starting in the low half of the transmit buffer. with the transmitter in the idle state, the processor would execute the following sequence: write byte 1 to address 0x30 write byte 2 to address 0x31 write byte 3 to address 0x32 write byte 4 to address 0x33 write 0x19 to address 0x01 (txbyte[2:0] = 011, txmsg = 1) at tx interrupt: write byte 5 to address 0x34 write byte 6 to address 0x35 write byte 7 to address 0x36 write byte 8 to address 0x37 write 0x39 to address 0x01 (txbyte[2:0] = 111, txmsg = 1) at tx interrupt: write byte 9 to address 0x30 write byte 10 to address 0x31 write 0x0b to address 0x01 (txbyte[2:0] = 001, txmsg = 1, txfcs = 1) at tx interrupt: write 00 to address 0x01 (txmsg = 0, txfcs = 0) 2.3.7 txfeac channel transmission the third c-bit in subframe 1 of the m-frame is the transmit far end alarm and control (txfeac) channel. this channel uses a bit-oriented protocol and is under control of the transmit feac channel byte register [cr03;0x03]. the txfeac channel transmitter is under control of the cbitp/dl, e3frm, and txalm[1,0] bits in the mode control register and the transmit feac channel message byte [txfeac[7:0];cr03.7:0] in the transmit feac channel byte register. an interrupt for use with txfeac channel operations is available on the dlint/sourcelb output pin and status bits for determining the interrupt source are located in the data link interrupt status register. the framer mode must be set to c-bit parity mode for txfeac channel transmission to take place. in c-bit parity mode, the last c-bit in subframe 1 of the m-frame will be used for transmission. there is no txfeac channel transmission in either e3 mode or with the cbitp/dl bit set to zero. setting extcbit in c-bit parity mode has no effect on txfeac channel transmission. setting the txalm[1,0] bits for transmission of ais or all ones in c-bit parity mode will disable transmission of the txfeac channel. transmission of yellow alarm or idle code in c-bit parity mode has no effect on txfeac channel transmission.
2.0 functional description cn8330 2.3 transmitter operation ds3/e3 framer with 52 mbps hdlc controller 2-16 conexant 100441e the transmit feac channel byte register controls the byte to be transmitted on the txfeac channel. all messages for transmission on this channel must be in the form ? 0xxxmmm011111111". the rightmost bit of this sequence is the first bit transmitted on the channel. to initiate transmission of a message byte in the txfeac channel, the desired byte in the form 0mmmxxx0 is written into the transmit feac channel byte register. transmission of the flag (11111111) is automatic. each time the message is sent, an interrupt will be issued on the dlint/sourcelb pin and will appear in the data link interrupt status register to request a new byte from the processor. the transmit feac channel byte register must be written to clear the interrupt. if multiple transmissions of the same byte are desired, the processor should rewrite the desired byte on each interrupt and count the interrupts until the desired number of transmissions have taken place. interrupts from the txfeac channel will occur at a rate of approximately one interrupt per 1.7 msec. transmit feac clears the internal data shift buffer after sending cr03 contents unless the host has again written to cr03. when the host writes cr03, cn8330 transfers cr03 contents to an internal data shift buffer and then immediately raises an interrupt (sr02.1) which tells the host that another codeword (or the same one) can be written. after the interrupt the host must write to cr03 within 1.7ms to keep sending codewords, else after sending the shift buffer contents cn8330 will automatically return to sending idle (all ones) feac codewords. in summary, transmit feac clears the internal data shift buffer after sending the transmit feac channel byte from the cr03 register contents unless the host has again written to this register (cr03). when the host writes to transmit feac channel byte register (cr03), cn8330 transfers the contents to an internal data shift buffer and then immediately raises an interrupt in the data link interrupt status register (sr02.1) which tells the host that another code word (or the same one) can be written. after the interrupt, the host must write to transmit feac channel byte register (cr03) within 1.7 ms to keep sending code words, or else after sending the shift buffer contents cn8330 will automatically return to sending idle (all ones) feac codewords. if a one is in either the msb or lsb position of the txfeac field, then continuous transmission of idle flags is enabled and no interrupts will be issued until a byte of the proper format is written to the transmit feac channel byte register. interrupts from the txfeac channel transmitter will appear on transmit feac channel interrupt bit. interrupts must be enabled to appear on dlint/sourcelb by setting the cbitp/dl bit in the mode control register. 2.3.8 ppdl transmitter the payload portion of the cn8330 data stream can come from an internal ppdl formatter that provides an external byte-wide data interface and a byte clock. this source is enabled by setting the paraen bit in the feature control register. the ppdl formatter is controlled by signals applied on the sndmsg and sndfcs pins. both byte-wide and nibble-wide inputs can be provided. optional hdlc formatting with 16-bit or 32-bit fcss is provided.
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.3 transmitter operation 100441e conexant 2-17 hdlc mode is selected by setting the paraen bit of the feature control register high and the disppdl bit of the ppdl control register low. operation is controlled by the sndmsg and sndfcs pins. if no message is in progress, idle flags (01111110) are continuously transmitted in the data payload. setting sndmsg high initiates message transmission. data bytes and control signals are provided in response to the rising edge of the txbck/txgapck pin and are sampled internally after the falling edge. the data and controls should be held for a full period. the lsb of the transmitted bytes is applied to tdat[0] and the msb to tdat[7]; transmission is lsb first. the transmitter performs automatic zero stuffing for transparency and fcs calculation for the data. the message must be an integral number of bytes in length. the fcs is 16 or 32 bits in length depending on the setting of the 32-bit crc select bit [crc32;cr05.2] in the ppdl control register. if this bit is low, a 16-bit fcs is calculated with the polynomial: x 16 +x 12 +x 5 +1 if the crc32 bit is high, a 32-bit fcs is calculated. sndfcs must be high for four cycles of the transmit byte clock and the fcs is calculated with the polynomial: x 32 +x 26 +x 23 +x 22 +x 16 +x 12 +x 11 +x 10 +x 8 +x 7 +x 5 +x 4 +x 2 +x+1 the fcs is transmitted by setting both the sndmsg and sndfcs pins high after the last data byte has been transmitted. an abort sequence may be transmitted by setting sndfcs high while sndmsg is set low. timing for the transmit operation is shown in figure 2-8 . figure 2-8. ppdl transmitter timing txcki sndmsg txbck/txgapck tdat[7:0] sndfcs data data
2.0 functional description cn8330 2.3 transmitter operation ds3/e3 framer with 52 mbps hdlc controller 2-18 conexant 100441e txbck/txgapck is generated from txcki and has a duty cycle of 25 percent. txbck will nominally be one-eighth the txcki frequency but is influenced by hdlc transparency bit insertions and ds3/e3 overhead bits. in the absence of any transparency bit insertions or overhead bits, there will be one pulse on txbck for every eight clock cycles of the txcki input. when a transparency bit is inserted into the serial transmit data stream, the txbck period will be lengthened to nine clock cycles of txcki (or up to 11 cycles if two transparency bit insertions and a ds3 overhead bit land in the same data octet interval). txbck/txgapck is present continuously even during the transmission of idle flags. the actual setup times on tdat[7:0], sndmsg, and sndfcs relative to the rising edge of txbck are negative. therefore, it is possible to read data and control from a ram or fifo buffer with the rising edge. the cn8330 will sample the data after the falling edge. this allows fifos or rams with access times of 35 ? 40 nsec to be used. the parallel interface can be used without transparency bit insertion by setting the disppdl bit in the ppdl control register to a 1. in this mode, sndmsg is held high and sndfcs is held low so that no flags or fcs bytes are transmitted. byte synchronization in the transmitter and receiver is achieved from the m-frame sync alignment. this allows the byte-wide interface to be used as the data input for non-hdlc payloads rather than the serial input pin. data is inserted on the tdat[7:0] pins in response to txbck/txgapck just as in the hdlc mode. data bytes are transmitted lsb first. if e3 mode is enabled, the transmitted bytes are byte aligned after the 16 overhead bits for a total of 190 bytes per frame. to accommodate e3 smds applications, the input bytes should be applied to the tdat[7:0] pins in reverse bit order so that the msb will be transmitted first.
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.3 transmitter operation 100441e conexant 2-19 the ppdl transmitter can be used with a nibble-wide interface for ds3 smds applications if desired. to enable nibble-wide transmission, both the nibble mode enable [nibble;cr05.0] and disppdl bits in the ppdl control register should be set to one. data should be inserted on the tdat[3:0] pins; msb on tdat[2], second msb on tdat[1], next msb on tdat[0], lsb on tdat[3] in response to txbck/txgapck (which now occurs every 4 bits). in nibble mode, the nibbles are transmitted msb first and are nibble-aligned after each overhead bit in the ds3 frame for a total of 21 nibbles per 85-bit data block. nibble mode should not be used for e3 applications. in this mode (nibble mode and ppdlonly pin = 0), the transmit ppdl interface shifts the serial data by one bit. this anomaly (only on the transmit side) can be remedied by the circuit shown in figure 2-9 . figure 2-9. nibble mode with the ppdlonly control pin low data bit input pin msb 2sb 1sb lsb q output tdat[2] tdat[1] tdat[0] d input tdat[3] q3 q2 q1 q0 ck nibble data register tdat[3] tdat[2] tdat[1] tdat[0] txbck cn8330 dq ck ? d-type ff
2.0 functional description cn8330 2.3 transmitter operation ds3/e3 framer with 52 mbps hdlc controller 2-20 conexant 100441e fcs calculation can be limited to the first n bytes of the transmitted message by setting the limit frame check sequence calculation [limitfcs;cr05.3] control bit. in this mode, the fcs is calculated on the first n bytes transmitted after the opening flag and then held until the end of the message. it is then appended to the end of the message in normal fashion. the desired number n can be from 1 to 16 (a value of 0 gives n=16) and is loaded in the frame check sequence calculation count [fcscnt[3:0];cr05.7:4] control field. this allows fcs calculation only on the header information in a t1 packet voice format. 2.3.9 ppdlonly mode the transmitter can be placed in a mode where the entire transmit stream consists of data with no ds3/e3 overhead bits inserted. this mode is enabled by providing a high input on the ppdlonly input pin. this mode allows the cn8330 to be used as a high-speed ppdl formatter and can be used at any clock rate up to the full 52 mhz capability of the device. data and controls are provided to the transmitter in response to the transmit byte clock. when ppdlonly mode is set, the transmit nrz data stream is available on the rxcck/txnrz pin. 2.3.10 transmitter outputs the txpos and txneg pins provide a variety of signals depending on the control bits in the feature control register. table 2-1 summarizes the available output combinations when the test equipment feature select bit [tsteqsel;cr04.7] is low. table 2-1. transmit encoding options disenc ami/lcv2 transmit output 0 0 b3zs/hdb3 encoded data on txpos, txneg 0 1 ami encoded data on txpos, txneg 1 0 nrz data on txpos, transmit clock on txneg 1 1 nrz data on txpos, transmit clock on txneg
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.3 transmitter operation 100441e conexant 2-21 2.3.11 test equipment specific features additional features in the transmitter are available if parallel mode is not selected (paraen = 0). the rdat[7]/txnrz pin becomes an output of the transmit data in nrz format before being presented to the b3zs/hdb3 encoder. the tdat[5]/txenci pin is an input directly to the b3zs/hdb3 encoder. this input is selected if the tsteqsel bit is set high. this allows either direct insertion of data for b3zs/hdb3 encoding or modification of the transmit data via rdat[7] and reinsertion of this stream for encoding. the tdat[4]/lcverri pin is an input that allows insertion of line code violations into the transmit data stream. this input is also enabled when the tsteqsel bit is set high. when enabled, a line code violation will be inserted at the next opportunity each time the lcverri pin is high. the input should be high for only one clock cycle to guarantee that only one line code violation is generated. if the ami/lcv2 control bit in the feature control register is low, a valid insertion opportunity is defined as the second 1 in a 11 sequence. if ami/lcv2 is high, a valid insertion opportunity is defined as the next b3zs/hdb3 substitution. the opposite polarity of substitution pattern will be inserted if an error is to be generated (a b0v/b00v instead of an 00v/000v or vice versa). this avoids the possibility of incorrectly emulating a b3zs/hdb3 substitution pattern and causing bit errors. note: b = legal bipolar pulse; v = bipolar violation pulse.
2.0 functional description cn8330 2.4 receiver operation ds3/e3 framer with 52 mbps hdlc controller 2-22 conexant 100441e 2.4 receiver operation 2.4.1 bipolar-to-unipolar conversion the bipolar-to-unipolar recovery circuit includes the b3zs/hdb3 decoding circuit. decoding is done according to tr-tsy-000009 for b3zs or g.703 for hdb3. a circuit detects the b3zs/hdb3 signature and the substitution back to three or four zeros is made. substitution to three or four zeros is made on every occurrence of 00v/b0v (b3zs) or 000v/b00v (hdb3). bipolar and line code violations (other than those associated with a valid b3zs/hdb3 signature) are counted in the 16-bit ds3/e3 lcv counter [sr12,sr13;0x25,0x26] that is cleared when read. in ds3 mode, a substitution pattern of improper polarity (b0v for 00v or vice versa) will be decoded to three zeros but will be counted as a bipolar violation. occurrences of three or more zeros before b3zs decoding will also be counted as a bipolar violation. in e3 mode, line code violations (lcvs) are counted in the ds3/e3 lcv counter. an lcv is defined by itu-t o.161 as two consecutive bpvs of the same polarity. occurrences of four or more zeros before hdb3 decoding will not be counted as an lcv. b3zs/hdb3 decoding can be defeated by connecting the rxpos and rxneg inputs together and supplying nrz input data to both pins or by setting the ami/lcv2 control bit high and supplying a non-encoded ami signal on rxpos and rxneg. 2.4.2 receive fifo the receiver circuit contains a 16-bit fifo buffer immediately following the b3zs decoding circuit to provide jitter elasticity of up to 5 unit intervals. the data is clocked into the fifo buffer with the incoming ds3cki clock. data is clocked out of the fifo buffer and into the remaining receiver circuitry by the rxcki which is a dejittered version of ds3cki. the fifo buffer circuit provides a vco control signal to indicate the phase relationship of the fifo buffer input and output clocks. both clocks are divided by 16 internally to derive the vco output as shown in figure 2-10 . this signal can be used to control the clock recovery circuit producing the smoothed rxcki. the fifo buffer circuit is bypassed and all receiver circuitry is clocked with ds3cki if fifen is low. rxcki should be tied to ground if the fifo buffer is disabled. figure 2-10. vco output signal timing rxcki 16 vco output ds3cki 16
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.4 receiver operation 100441e conexant 2-23 2.4.3 received signal output the received unipolar signal is recovered and provided with a clock on rxdat and rxclk. an m-frame synchronization signal and gapped clock are also provided. figure 2-11 shows a timing diagram for ds3 mode with negligible propagation delays for the ds3 receiver output signals. refer to the electrical and mechanical specifications section for actual propagation delay specifications. rxmsy is low during subframe 7 preceding the x1 bit in the first subframe. outputs change on the rising edge of the receive clock except for the gapped clock on rxbck/rxgapck. this clock is an inverted version of rxclk with a gapped pulse every 85 bits. the receive clock will be nominally 44.736 mhz. data on rxdat can be clocked into the user's circuit with the rising edge of the rxbck/rxgapck if it is desired to observe only data bits (there is no rising edge present during the overhead bit positions). the rising edge of rxbck will be mid-bit for each payload bit in the serial stream. an overhead indicator rdat[6]/rxovh is available when the ppdl is not enabled. this signal is low for each bit position that is an overhead bit in the receive serial stream. figure 2-11. receiver timing for serial ds3 mode rxclk rdat[6]/ rxovh rxbck/ rxgapck rxmsy subframe 1 84 info bits x1 84 info bits subframe 7 f4 rxdat
2.0 functional description cn8330 2.4 receiver operation ds3/e3 framer with 52 mbps hdlc controller 2-24 conexant 100441e figure 2-12 illustrates the receiver timing for the parallel ds3 mode. this mode is enabled by setting the paraen bit in the feature control register and setting the disppdl bit in the ppdl control register. the receive data is valid on either the rising or falling edge of rxbck. figure 2-13 illustrates a timing diagram for the e3 receiver output signal with the ppdl enabled. the clock and data edge relationships are similar to those in ds3 mode. the m-frame synchronization signal rxmsy is high during the 12-bit block corresponding to the 10-bit fas and the a and n bits. if the ppdl is enabled, the m-frame synchronization signal will be high for four additional bit periods corresponding to the 1100 pattern found in smds formatted signals. rdat[6]/rxovh will be low for 12 bits in serial mode and for 16 bits if the ppdl is enabled. figure 2-12. receiver timing for parallel ds3 mode data data data data data subframe 7 subframe 1 rxclk rxmsy rxbck/ rxgapck rdat[7:0] figure 2-13. e3 receiver output timing rxclk rdat[6]/ rxovh rxbck/ r xgapck rxmsy info bits 10-bit fas low for 12 or 16 bits rxdat 1520/1524 info bits high for 12 or 16 bits a/n/1100
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.4 receiver operation 100441e conexant 2-25 2.4.4 framing operation in ds3 mode, a parallel search framing circuit is used to recover the subframe and m-frame alignments in the ds3 signal. framing is initiated by an out-of-frame (oof) condition as determined by the receiver frame bit check circuitry. when 3 out of 16 consecutive subframing (f) bits are in error or when 2 out of 3 consecutive m-frames have m bit errors, an oof condition is declared. average reframe time is less than 1 msec. in e3 mode, a serial search for the 10-bit fas pattern (1111 0100 00) is conducted. when three consecutive correct patterns are found, the receiver is declared to be in frame. an oof condition is declared when four consecutive incorrect fas patterns are detected. average reframe time is less than 250 sec. in either mode, serial data continues to be present on rxdat and rxmsy and will continue to indicate the old framing position until the oof condition clears. rxmsy will indicate the new framing position when the oof condition is cleared. 2.4.5 alarm detection the cn8330 receiver contains status indicators to obtain alarm information for link maintenance. alarm indication signal detect [aisdet;sr00.2] in the ds3/e3 maintenance status register [sr00;0x10] is updated each m-frame interval. it is set if ais was detected in the previous m-frame. an ais condition is present when there is valid framing and parity, both x-bits are equal, all c-bits are zero, and the payload bits are 1010... starting with 10 after each overhead bit. this signal can be integrated by the controller to declare a received ais. in e3 mode, an unframed all-ones signal is detected as ais. idle code detect [idledet;sr00.4] is updated each m-frame interval. it is set if the idle code condition was detected in the previous m-frame. the idle code condition is present when there is valid framing and parity, both x-bits are equal, all c-bits in subframe 3 are zero, and the payload bits are 1100... starting with 11 after each overhead bit. no idle code is defined for e3 signals; therefore, idledet will indicate zero in e3 mode. yellow alarm detect [yeldet;sr00.3] is updated each m-frame interval and is an active high indication that both x-bits in the previous m-frame were low. this indication will not be set if the x-bits are in disagreement or if both x-bits are high. in e3 mode, yeldet will be set if the a-bit is high. loss-of-signal alarm [losalm;sr00.0] is set as soon as 175 75 consecutive zeros (prior to b3zs/hdb3 decoding) are received. this alarm condition is set as soon as the condition is detected. the indication is cleared when a one's density of more than 33 percent (25 percent for e3) is achieved for 175 75 clock cycles. note that in some systems, a loss-of-signal alarm is not cleared until the receiver is in frame. this function can be performed by the controller.
2.0 functional description cn8330 2.4 receiver operation ds3/e3 framer with 52 mbps hdlc controller 2-26 conexant 100441e the frame bits are monitored to determine errors and oof conditions. the oof indicator is set whenever 3 of 16 consecutive f framing bits are in error or when 2 of 3 consecutive m-frames have m-bit errors in ds3 mode. in e3 mode, four consecutive occurrences of an incorrect fas will result in an oof condition. auxiliary error indication outputs are available when the ppdl is not enabled. a 1-bit-period-wide pulse for each f- or m-bit error or each incorrect fas is available on the rdat[4]/frmerr pin. indications of los, oof, ais, and idle are available on rdat[0:3], respectively. these indications are not internally latched and do not require action from the microprocessor to clear. 2.4.6 terminal data link reception lapd receiver logic for the terminal data link in c-bit parity format is included in the framer circuit. data link reception is also provided for the n-bit in e3 mode. this logic manages an 8-byte message buffer for the data link receiver. idle and abort flag detection, fcs checking, and stuffed zero removal are also included. microprocessor interrupts are used to synchronize the passing of data to and from the message buffer. the terminal data link receiver is under the control of the received data stream only. the receiver interrupt is under the control of receive data link interrupt enable [rxtdlie;cr01.7] in the terminal data link control register and cbitp/dl in the mode control register. this interrupt must be enabled by setting both of these bits for receiver interrupts to appear on the dlint/sourcelb output and for proper interaction with the processor. the c-bits in subframe 5 in c-bit parity mode or standard ds3 mode (the n-bit in e3 mode) are provided to the receiver circuitry at all times. therefore, when the ds3/e3 maintenance status register indicates that alarms are being received rendering the data link information useless, it may be desirable to disable the rxtdlie bit to prevent excessive or spurious interrupts to the processor. receiver status is monitored via receive terminal data link interrupt [rxtdlitr;sr02.2] in the data link interrupt status register and via the terminal data link status register [sr04;0x14]. when a receive data link interrupt is generated on dlint/sourcelb, the rxtdlitr bit will be set in the data link interrupt status register. if this bit is observed upon reading the data link interrupt status register, then the terminal data link status register should be read to get the receiver status that caused the interrupt. the terminal data link status register contains 3 status bits and a 3-bit buffer pointer. the status bits are abort flag received [rxabort;sr04.0], bad fcs [badfcs;sr04.1], and idle code received [rxidle;sr04.2]. the 3-bit buffer pointer, byte received [rxbyte[2:0];sr04.5:3], is used to point to locations in the 8-byte receive terminal data link message buffer [rxtdl;0x40 ? 0x47]. the buffer pointer indicates the last location written by the data link receiver. the receiver implements a lapd data link per ccitt standard q.921. the functions provided by the data link receiver circuitry are transparency zero removal, fcs checking, idle flag reception, and abort flag reception. there are no restrictions on the total length of the message. q.921 requires all messages be an integral number of 8-bit bytes. if the receiver receives a message that is not an integral number of bytes, the receiver status will indicate a message received with bad fcs. the per-byte reception time is approximately 284 microseconds in c-bit parity mode and approximately 357 microseconds in e3 mode.
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.4 receiver operation 100441e conexant 2-27 the receiver powers up in an indeterminate state. it is initialized by the receipt of an idle flag (0x7e) on the link, which sets rxidle = 1 in the terminal data link status register. when the idle flag is removed from the link and a message starts coming in, the receiver removes stuffed zeros and writes the resulting data to the receive terminal data link message buffer beginning with address 0x40 and counting up to 0x47. when the first four addresses have been written, the processor is interrupted to read the data out of the buffer. the processor has four byte intervals (at least 1 msec) to read the data before it is overwritten with new data. the interrupt is cleared when the processor reads the terminal data link register. this register will indicate a message in progress at this time (rxidle = 0, rxbyte[2:0] = 3). if the upper half of the buffer had just been filled, the status register will indicate rxbyte[2:0] = 111 and locations 4 through 7 must be read during the next four byte intervals to retrieve the message. when the last block of data has been received, the processor will again be interrupted. this time the terminal data link status register will indicate the end of message (rxidle = 1, rxbyte[2:0] = n, badfcs = 0 or 1). the rxbyte[2:0] = n portion of the register indicates the highest numbered location that was written in the receive buffer. locations 0 to n or 4 to m (where n = 0 to 3 and m = 4 to 7) must be read to retrieve the data depending on what has already been read at the previous interrupt. the two highest numbered locations contain the fcs that was received at the end of the message. a new incoming message will always start in the opposite buffer half from where the previous message ended to prevent overwriting of previously received bytes and allow the processor time to retrieve those bytes. for example, if a message ended in buffer address 0x44, 0x45, 0x46, or 0x47, the next message received would be stored beginning in address 0x40. if a message ended in buffer address 0x40, 0x41, 0x42, or 0x43, the next message received would be stored beginning in address 0x44. if the received message is a multiple of 8 bytes, then when the processor is interrupted to read the last block of data, the fcs has yet to be received. in this event, the processor will again be interrupted when the fcs has been checked and an idle flag is received. the terminal data link status register will show rxbyte[2:0] = 001 (or 101), badfcs = 0 or 1, and rxidle = 1; and the fcs received will be in locations 0 and 1 (or 4 and 5). again, the data must be read out during the next four byte intervals, or it may be overwritten by a new incoming message. alternatively, the fcs data may be ignored, and the good or bad indication used directly. it is important that software strategies allow for the fact that the lapd receiver cannot recognize the fcs as such until the closing flag is recognized. it can happen that the processor is interrupted to read four message bytes, and the next byte received is the closing flag. when the processor exits the interrupt routine, another interrupt will be pending for the end of message. the status for this interrupt will indicate the idle condition, the fcs status, and the byte count will be the same as the previous interrupt (rxbyte[2:0] = 011 or 111) because no extra bytes were received. in this event, the last two bytes read from memory on the previous interrupt were not message bytes after all, but were actually the fcs bytes. if the fcs spans a 4-byte boundary, the final interrupt will indicate the idle condition, the fcs status, and that one additional byte was received (rxbyte[2:0] = 000 or 100).
2.0 functional description cn8330 2.4 receiver operation ds3/e3 framer with 52 mbps hdlc controller 2-28 conexant 100441e 2.4.6.1 receiver interrupts the data link receiver generates an interrupt in response to three events: the current half of the message buffer is full, the end-of-message flag was detected, or an abort flag was detected. the terminal data link status register indicates the cause of the interrupt. the interrupt will be cleared upon the reading of this register. if the interrupt is due to the current half of the receive buffer being full, rxidle will be cleared, and rxbyte[2:0] will indicate which half of the buffer must be read. if the interrupt is due to the end-of-message flag being detected, rxidle will be set, badfcs will indicate the result of the fcs error check, and rxbyte[2:0] will indicate the last location written. the processor will not be interrupted again until 4 bytes of a new message have been received. if the interrupt is due to an abort flag being received, abort will be set, and there is nothing to do other than discard any previously received message bytes. the processor will not be interrupted again until 4 bytes of a new message have been received. interrupts from the terminal data link receiver will appear on rxtdlitr in the data link interrupt status register. interrupts must be enabled to appear on dlint/sourcelb by setting the cbitp/dl bit in the mode control register and rxtdlie bit in the terminal data link control register in either c-bit parity mode or e3 mode. 2.4.6.2 receiver response example the following example shows the sequence necessary to receive an 8-byte hex message that is stored starting in the lower half of the receive buffer. the final interrupt indicates that two more bytes are present in the buffer but these bytes are fcs bytes, not message bytes. when an interrupt is received, the processor reads the data link interrupt status register to determine the source of the interrupt. if the source is determined to be the receive terminal data link, the processor will respond in the following manner: at rx interrupt: read address 0x14 to get status (status = 0x18: rxbyte[2:0] = 011, rxidle = 0) read address 0x40 to get 1st data byte read address 0x41 to get 2nd data byte read address 0x42 to get 3rd data byte read address 0x43 to get 4th data byte at rx interrupt: read address 0x14 to get status (status = 0x38: rxbyte[2:0] = 111, rxidle = 0) read address 0x44 to get 5th data byte read address 0x45 to get 6th data byte read address 0x46 to get 7th data byte read address 0x47 to get 8th data byte at rx interrupt: read address 0x14 to get status (status = 0x0c or 0x0e: rxbyte[2:0] = 001, rxidle = 1, badfcs = 0 or 1) read address 0x40 if desired (fcs byte 1) read address 0x41 if desired (fcs byte 2)
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.4 receiver operation 100441e conexant 2-29 2.4.7 rxfeac channel reception receiver logic is provided for reception of the receive far end alarm and control (rxfeac) channel which is present in c-bit parity mode. this channel uses a bit-oriented protocol and received data is provided in the receive feac channel byte register [sr03;0x13]. the rxfeac channel receiver is under control only of the received data stream. the receiver interrupt is under control of receive feac interrupt enable [rxfeacie;cr02.6] in the status interrupt control register and the cbitp/dl bit in the mode control register. this interrupt must be enabled by setting both of these bits for receiver interrupts to appear on the dlint/sourcelb output and for proper interaction with the processor. the last c-bit in subframe 1 in c-bit parity mode or in m13 mode is provided to the receiver circuitry at all times. there is no rxfeac channel capability in e3 mode. therefore, when e3 mode is selected with cbitp/dl set or when the mode control register indicates that alarms are being received rendering the data link information useless, it may be desirable to disable the receive feac interrupt via the rxfeacie bit to prevent excessive or spurious interrupts to the processor. receiver status is monitored via the receive feac channel interrupt [rxfeacitr;sr02.0]. when an rxfeac channel interrupt is generated on dlint/sourcelb, the rxfeacitr bit will be set in the data link interrupt status register. if this bit is observed to be a 1 upon reading the data link interrupt status register, then another byte has been received and placed in the receive feac channel byte register. an idle message is all-ones and all other messages are of the form ? 0xxxmmm011111111 ? with reception of the rightmost bit first from the channel. the receiver logic recognizes the eight ones message flag followed by a message byte and interrupts the controller upon reception of a valid message byte. the ? 0mmmxxx0 ? message byte that was received is stored in the receive feac channel byte register. continuous incoming messages on the rxfeac channel will produce an interrupt rate of approximately one interrupt per 1.7 msec for this interrupt source. no interrupts are generated if the rxfeac channel is receiving continuous idle flags, the interrupt is not enabled in the status interrupt control register, or cbitp/dl bit is not set. reading the receive feac channel byte register clears the interrupt. interrupts from the rxfeac channel receiver will appear on the rxfeacitr. interrupts must be enabled to appear on dlint/sourcelb by setting both cbitp/dl in the mode control register and the rxfeacie bit in the status interrupt control register.
2.0 functional description cn8330 2.4 receiver operation ds3/e3 framer with 52 mbps hdlc controller 2-30 conexant 100441e 2.4.8 ppdl receiver the receiver circuitry contains a ppdl receiver for the payload portion of the cn8330 data that is activated when the paraen bit in the feature control register is set. this receiver performs idle flag detection, stuffed zero deletion, and fcs checking on the incoming data stream. the recovered data bytes are presented on rdat[7:0] and are valid on both the rising and falling edges of rxbck/rxgapck. the lsb is on rdat[0] and the msb on rdat[7]/txnrz; the lsb is the first received from the serial input. if the payload stream contains idle flags, the idle pin will be high and the flags will be present on rdat[7:0]. if a valid fcs is received at the end of the message block, the valfcs/txovh pin will be active high while idle/frmcar is high. at the start of the next message, both indications will go low until the end of the incoming message has been received. if a bad fcs is received, idle/frmcar will go high and valfcs/txovh will remain low. if valfcs/txovh goes high and idle/frmcar does not, an abort sequence was received in the data. if there is only one flag received between incoming packets, there will be only one rxbck/rxgapck pulse present while idle/frmcar is high. if the 32-bit crc select bit (crc32;cr05.2) is low, the fcs is checked with the polynomial: x 16 +x 12 +x 5 +1 if 32-bit crc is selected by setting the crc32 bit high, then the fcs is checked with the polynomial: x 32 +x 26 +x 23 +x 22 +x 16 +x 12 +x 11 +x 10 + x 8 +x 7 +x 5 +x 4 +x 2 +x+1
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.4 receiver operation 100441e conexant 2-31 timing for this operation is shown in figure 2-14 . illustrated are cases of a good packet received, a packet received with a bad fcs, and an aborted packet. each packet is shown with one idle flag marking the end of the packet and the start of the next packet. however, more than one flag can occur in the serial stream. the output data will contain each occurrence of idle or abort flags with a pulse on rxbck/rxgapck. rxbck/rxgapck is generated from the falling edge of the receive serial clock input (either ds3cki or rxcki depending on fifen) and is present continuously like the transmit byte clock. nominally there will be one pulse on rxbck/rxgapck for every eight clock cycles on the receive serial clock. when an inserted transparency bit must be deleted or ds3/e3 overhead bits skipped, the rxbck/rxgapck period will be lengthened by one or more serial clock cycles. rxbck/rxgapck is present during the reception of fcs octets and idle flags. the rdat[7:0], idle/frmcar, and valfcs/txovh outputs are valid at least one serial clock cycle period before the rising edge of rxbck/rxgapck and are valid for at least two serial clock cycle periods after the falling edge of rxbck/rxgapck. figure 2-14. ppdl receiver timing rxclk idle/frmcar rxbck/ rxgapck rdat[7:0] valfcs/ txovh abort data data flag valfcs/ txovh idle/frmcar valfcs/ txovh idle/frmcar rdat[7:0] data flag data data good packet packet w/bad fcs aborted packet
2.0 functional description cn8330 2.4 receiver operation ds3/e3 framer with 52 mbps hdlc controller 2-32 conexant 100441e the parallel interface can be used without transparency bit deletion by setting the disppdl bit in the ppdl control register to a 1. in this mode, byte synchronization in the transmitter and receiver is achieved from the m-frame sync alignment and zeros detected after strings of five ones are not deleted. this allows the byte-wide interface to be used as the data output in normal ds3/e3 mode rather than the serial output pin. the idle/frmcar and valfcs/txovh indications are ignored when operating in this mode. data bytes are received with the same timing relative to rxbck/rxgapck as in hdlc mode. in e3 mode, 190 bytes per frame will be received with byte alignment after the 16 overhead bits (fas, a, n, 1100). the ppdl receiver can be used with a nibble-wide interface for ds3 smds applications if desired. to enable nibble-wide transmission, both the nibble mode enable and disppdl bit controls in the ppdl control register should be set to 1. received data is available on the least significant nibble of the rdat[7:0] pins with the same timing relative to rxbck/rxgapck (which now occurs every 4 bits). in nibble mode, the nibbles are received msb first, with the msb on rdat[3], 2sb on rdat[2], 1sb on rdat[1], and the lsb on rdat[0]. for e3 smds applications, the byte-wide interface should be used. fcs checking can be limited to the first n bytes of the received message by setting the limitfcs control bit in the ppdl control register. in this mode, the fcs is checked only on the first n bytes received after the opening flag and then held until the end of the message. the locally calculated fcs is then compared to the last two/four bytes in the message to determine if a valid fcs was received. the desired number n can be from 1 to 16 (a value of 0 gives n = 16) and is loaded in the fcscnt[3:0] control field in the ppdl control register. this allows fcs checking only on the header information in a t1 packet voice format. 2.4.9 ppdlonly mode the receiver can be placed in a mode where the entire receive stream is expected to be data with no ds3/e3 overhead bits inserted. this mode is enabled by providing a high input on the ppdlonly input pin. this mode allows the ic to be used as a high-speed ppdl receiver and can be used at any clock rate up to the full 52 mhz capability of the device. this data interface is described in the ppdl receiver section of this chapter.
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.4 receiver operation 100441e conexant 2-33 2.4.10 serial c-bit output all received c-bits are output on the cbito pin on the rising edge of rxcck/tznrz in ds3 mode. this allows external circuitry to examine individual c-bits if necessary. the timing is shown in figure 2-15 . the received n-bits are output on the cbito pin on the rising edge of rxcck/tznrz in e3 mode. this allows external circuitry to process the n-bit if necessary. the relative timing is the same as in ds3 mode except there is only one n-bit per frame. figure 2-15. c-bit output timing rxcck/txnrz cbito subframe 1 subframe 7 subframe 2 subframe 6 c2 c1 c2 c3 c1 c3 c1 c2 c3 c1 c2 c3
2.0 functional description cn8330 2.5 monitor mode for stand-alone operation ds3/e3 framer with 52 mbps hdlc controller 2-34 conexant 100441e 2.5 monitor mode for stand-alone operation operation without a microprocessor is possible with the mon/mic* pin tied high. in this mode of operation, the transmitter is set to m13 format with external c-bit insert [extcbit;cr00.2] enabled. e3 mode operation is not available without a microprocessor. external circuitry must format all of the c-bit locations to the desired values and present them on the cbiti pin in response to the txcck clock output. proper c-bit ordering can be determined by the relationship to the input or output m-frame syncs (tdat[7]/txsyi or txsyo). the parallel data input port for the ppdl transmitter is enabled by setting the paren input high. setting the crc32 input high selects the 32-bit crc mode. two special modes are available when in stand-alone operation. when the paren input is high and the ppdlonly input is low, the byte-wide interfaces are enabled with transparency bit insertion/deletion disabled. this allows the cn8330 to be used as a ds3 device with a parallel interface. when the paren input is high and the ppdlonly input is high, the byte-wide interfaces are enabled. transparency bit insertion/deletion is enabled. ds3 framing is disabled. this allows the cn8330 to be used as a high-speed hdlc formatter. the transmit serial data stream is available in nrz format on the rxcck pin in this mode. alarm generation in this mode is controlled by the cs/alm0 and rd*/alm1 pins. setting these pins, as described under mode control register in the registers chapter of this document, will enable transmission of the specified alarm signal (the txalm[1:0] bits work identically to the pins). the receiver will monitor all ds3 maintenance alarms and indications and provide occurrences of any alarm on the frmerr, lcv, par, idle, yel, ais, oof, and los pins (ad[6:0]). these indications can then be counted by external circuitry for appropriate action. the received data is present on the rxdat pin and, if the parallel port is enabled, on the rdat[7:0] pins. all c-bits are clocked out on cbito for external processing.
cn8330 2.0 functional description ds3/e3 framer with 52 mbps hdlc controller 2.5 monitor mode for stand-alone operation 100441e conexant 2-35 2.5.1 ds3 monitor mode error outputs if stand-alone monitor mode is selected by tying the mon/mic* pin high, then the cn8330 operates without a microprocessor and the eight address/data pins (ad[7:0]) of the microprocessor interface become ds3 alarm and error indication outputs (note that e3 framing is not available in monitor mode). outputs are provided for los, oof, ais, yellow alarm (x-bit low or a-bit high), idle code detect, parity errors, lcvs, and frame bit errors. all indications except lcv and frame bit errors are level indications and can be counted externally on a per m-frame basis, if desired. the frame error output is a pulse for each error in the m- or f-bit positions and can drive a counter directly. the lcv output will be high for every bit position that is an lcv and can be used with the rxclk output to facilitate external counting. all indications are active high and can be used to indicate the presence of the condition without reference to the clock output. figure 2-16 illustrates an lcv indication. the lcv indications are delayed from the pulse inputs due to b3zs decoding. monitor mode is supported only in ds3 mode. standalone e3 and hdlc monitor mode is not supported. figure 2-16. monitor mode error indication timing ds3cki rxpos rxneg ad[6]/lcv
2.0 functional description cn8330 2.5 monitor mode for stand-alone operation ds3/e3 framer with 52 mbps hdlc controller 2-36 conexant 100441e
100441e conexant 3-1 3 3.0 registers for a summary of all registers, refer to the register summary section at the end of this chapter. 3.1 control registers 0x00?mode control register (cr00) linelp line loopback enable ? set to enable the loopback in the external direction (back to network). this loopback connects the received data stream before b3zs/hdb3 decoding to the transmitter. all data and overhead bits are looped; and bipolar violations (bpvs) are fully preserved per ansi standard t1.404. the received data is still presented to all receiver blocks and is present on the receiver output pins. sourcelp source loopback enable ? set to enable the loopback in the internal direction. this loopback connects the encoded transmitter data and clock directly to the receiver b3zs/hdb3 decoder. transmission of data on the line is not affected by this loopback. txalm1,0 transmit alarm control ? u sed to control transmission of various alarm signals. in ds3 mode, the ais, idle, and yellow alarm signals on the outgoing ds3 stream are controlled as follows: in e3 mode, the txalm0 bit should be set high to transmit the e3 ais signal and the txalm1 bit is set high to transmit the e3 yellow alarm (a-bit high). txalm0 bit has precedence in e3 mode. 7 6 5 4 3 2 1 0 linelp sourcelp txalm1 txalm0 extovh extcbit e3frm cbitp/dl txalm1 txalm0 alarm action 0 0 normal, no alarms transmitted 0 1 yellow alarm (x-bits low) transmitted 1 0 idle code transmitted 1 1 ais transmitted
3.0 registers cn8330 3.1 control registers ds3/e3 framer with 52 mbps hdlc controller 3-2 conexant 100441e extovh external overhead insert ? set to a 1 to enable insertion of the overhead bits (ds3: x, p, m, and f or e3: fas, a, and n) from the transmit serial data stream. extcbit external c-bit insert ? used to control insertion of data in the c-bit or n-bit positions of the transmit data stream. in ds3 mode, the c-bits are controlled as follows: u in e3 mode, external c-bit insert controls insertion of data in the n-bit position of the e3 data stream. the n-bit will come from the cbiti pin when extcbit is high, and from the terminal data link transmitter when extcbit is low. e3frm e3 framing mode ? enables the e3 mode framing and transmission circuitry. this control bit has priority over the c-bit parity mode/enable dlint bit. framing insertion and recovery is performed as specified in itu ? t g.751 cbitp/dl c-bit parity mode/enable dlint ? selects which type of framing is present on the transmitted ds3 signal. if this bit is low, then the basic ds3 framing mode is used. if this control bit is high, then the c-bit positions are used for the febe, feac, terminal data link, path parity, and mode indicator bits as defined in t1.107a-1989. when the e3 framing mode bit is high, this bit enables interrupts on the dlint/sourcelb output pin. c-bit parity mode ext. c-bit insert c-bit source 0 0 serial data stream 01 cbiti pin 1 0 all c-bits internally generated 1 1 internal except cp and febe from cbiti pin
cn8330 3.0 registers ds3/e3 framer with 52 mbps hdlc controller 3.1 control registers 100441e conexant 3-3 0x01?terminal data link control register (cr01) this terminal data link control register controls functions of the terminal data link as defined in c-bit parity or e3 mode. if c-bit parity or e3 mode is not selected, the contents of this register are ignored. rxtdlie receive terminal data link interrupt enable ? e nables the receive terminal data link interrupt bit [rxtdlitr;sr02.2] to appear on the dlint/sourcelb output pin. distxtdl disable transmit terminal data link ? forces the output of the transmit terminal data link to all ones. txbyte[2:0] byte ? a 3-bit pointer to the transmit terminal data link message buffer [txtdl;0x30 ? 0x37] address containing the last byte to be transmitted. txabort abort message ? causes the data link transmitter to halt the message in progress, send an abort flag, and then resume transmission of idle flags on the data link. txfcs send frame check sequence ? u sed to control the transmission of the fcs at the end of a message block. txmsg send message ? instructs the transmitter to begin transmission of a message block on the terminal data link. setting this bit removes the data link from idle flag transmission mode and enables interrupts to the controller for data bytes. 0x02?status interrupt control register (cr02) the status interrupt control register is provided to enable or disable individual interrupt sources. to enable an interrupt from a particular source, the control bit corresponding to that source must be set high in the interrupt control register. this enables the interrupt from that source to appear on the cntint/linelb output pin. if a source has its interrupt control bit set low, then interrupts from this counter will be masked from appearing on cntint/linelb. sr6ie shadow register interrupt enable ? a control bit that allows interrupts from the shadow status register [sr06;0x16] to appear on the cntint/linelb output pin. rxfeacie receive feac interrupt enable ? a control bit that allows interrupts from the feac receiver to appear on the dlint/sourcelb output pin when in c-bit parity mode. lcvctrie line code violation counter interrupt enable ? a control bit that allows interrupts from the ds3/e3lcv counter [sr12,sr13;0x25,0x26] to appear on the cntint/linelb output pin. febectrie febe event counter interrupt enable ? a control bit that allows interrupts from the ds3 febe event counter [sr11;0x24] to appear on the cntint/linelb output pin. pthctrie path parity error counter interrupt enable ? a control bit that allows interrupts from the path parity error counter [sr10;0x23] to appear on the cntint/linelb output pin. ferrctrie frame error counter interrupt enable ? a control bit that allows interrupts from the frame error counter [sr09;0x22] to appear on the cntint/linelb output pin. 7 6 5 4 3 2 1 0 rxtdlie distxtdl txbyte[2] txbyte[1] txbyte[0] txabort txfcs txmsg 7 6 5 4 3 2 1 0 sr6ie rxfeacie lcvctrie febectrie pthctrie ferrctrie dgrctrie parctrle
3.0 registers cn8330 3.1 control registers ds3/e3 framer with 52 mbps hdlc controller 3-4 conexant 100441e dgrctrie disagreement counter interrupt enable ? a control bit that allows interrupts from the ds3 disagreement counter [sr08;0x21]to appear on the cntint/linelb output pin. parctrie parity error counter interrupt enable ? a control bit that allows interrupts from the ds3 parity error counter [sr07;0x20]to appear on the cntint/linelb output pin. 0x03?transmit feac channel byte (cr03) txfeac[7:0] transmit feac channel message byte ? if the mode is set to c-bit parity, this register will be used as the data byte for the transmit feac channel transmitter. when this byte is in the form '0xxxxxx0' it is transmitted after every flag. if there is a one in either the most significant or least significant bit of this register, all ones (idle) will be transmitted on the data link and interrupts from this source will be disabled. writing to this register clears the transmit feac channel interrupt bit [txfeacitr;sr02.1] in the data link interrupt status register [sr02;0x12]. 0x04?feature control register (cr04) the feature control register is provided to enable or disable miscellaneous features in the cn8330. tsteqsel test equipment feature select ? set high to enable direct access to the b3zs/hdb3 encoder and to enable insertion of lcvs via the tdat[5]/txenci and tdat[4]/lcverri pins, respectively. normal operation of the transmitter is enabled when this bit is low. ami/lcv2 ami mode/lcv type 2 ? set high to enable ami outputs on txpos and txneg (no b3zs/hdb3 encoding). if the test equipment feature select bit is also set high, then this bit selects the type of lcv errors created when tdat[4]/lcverri is active (see table 2-1). disenc disable b3zs/hdb3 encoding ? set high to disable the b3zs/hdb3 encoder circuit and provide a unipolar nrz output instead of b3zs/hdb3 encoded output pulses. the unipolar output appears at the txpos pin and the ds3/e3 input clock is available on the txneg pin (see table 2-1). dislcv/ferr disable saturation of line code violation/frame errors ? set to allow the lcv and frame error counters to continue counting when the maximum count has been received without enabling the respective interrupt. this is for use with the carry output indications for these counters as described in ds3/e3 error counters section in this chapter. paraen parallel data enable ? set high to enable the ppdl transmitter and receiver as the source and sink for data. eight-bit data bytes on the tdat[7:0] and rdat[7:0] buses for the ppdl transmitter and receiver are provided. in e3 mode, the overhead field is also altered as described in framing-bit generation under the transmitter operation section in the functional description chapter. if this control bit is low, the tdat[6]/txdati and rxdat data lines are the data input and output, respectively, for the ds3/e3 stream. 7 6 5 4 3 2 1 0 txfeac[7] txfeac[6] txfeac[5] txfeac[4] txfeac[3] txfeac[2] txfeac[1] txfeac[0] 7 6 5 4 3 2 1 0 tsteqsel ami/lcv2 disenc dislcv/ferr paraen febec[3] febec[2] febec[1]
cn8330 3.0 registers ds3/e3 framer with 52 mbps hdlc controller 3.1 control registers 100441e conexant 3-5 febec[3:1] febe pattern bit field ? set to the 3-bit sequence that is to be sent each time a febe indication is to be transmitted in c-bit parity mode. this pattern is automatically transmitted when the receiver detects an f-bit or path parity error. the pattern must be anything other than all ones to indicate a febe to the far end. an all-ones pattern will disable febe transmission and should not be used for any other purpose. 0x05?ppdl control register (cr05) the ppdl control register is provided to control the mode of operation of the ppdl transmitter and receiver. fcscnt[3:0] frame check sequence calculation count ? determines the number of bytes over which the fcs is to be calculated. the number of bytes for calculation can be from 1 to 16 (a value of 0 results in 16 bytes of calculation). limitfcs limit frame check sequence calculation ? set to enable fcs calculation only on the first n bytes of an hdlc frame where n is determined by the fcs calculation count field. if this bit is low, the fcs will be calculated over all transmitted bytes. crc32 32-bit cycle redundancy check ? set high to enable 32-bit crc generation and checking on the ppdl. if this bit is low, then 16-bit crc generation and checking is enabled. disppdl disable ppdl transparency bit ? set high to disable insertion and removal of hdlc transparency bits in the ppdl transmitter and receiver. if this control bit is low, then normal insertion and removal of hdlc transparency bits will occur. nibble nibble mode enable ? set to enable the nibble mode interface to the ppdl transmitter and receiver for use in ds3 smds/802.6 applications. the disable ppdl transparency bit should be set high when nibble mode is enabled. 7 6 5 4 3 2 1 0 fcscnt[3] fcscnt[2] fcscnt[1] fcscnt[0] limitfcs crc32 disppdl nibble
3.0 registers cn8330 3.2 status registers ds3/e3 framer with 52 mbps hdlc controller 3-6 conexant 100441e 3.2 status registers there are six status registers: five for ds3/e3 status and one to indicate the version number of the ic. also included is a shadow register for the ds3/e3 maintenance status to latch status indications until read. the contents of these registers are described here and summarized in the register summary at the end of this section. the status signals are contained in latches and are applied to the controller data bus on the appropriate read command from the controller. the active state of all bits in the status registers is high. 0x10?ds3/e3 maintenance status register (sr00) the ds3/e3 maintenance status register contains the major ds3/e3 maintenance indicators. alarm detection details can be found in alarm detection in the receiver operation section of the functional description chapter. refrm reframe in progress ? set while the framing circuit is searching for a valid framing pattern in either ds3 or e3 modes. frmtid1,0 format identification ? identifies the incoming format based on the contents of the application id channel contained in the first c-bit of subframe 1. this bit pair will be set to 00 to indicate m13 format, 01 to indicate c-bit parity format, and 10 to indicate syntran format. in e3 mode, these bits are meaningless and should be ignored. idledet idle code detect ? set if there is valid framing and parity, the three c-bits in subframe 3 are zero, both x-bits are equal, and the payload contains a 1100... pattern starting with an 11 after each overhead bit in ds3 mode. this bit will be low in e3 mode since there is no defined e3 idle signal. yeldet yellow alarm detect ? set for one m-frame interval when both x-bits are low in the previous m-frame in ds3 mode. this bit is set when the received a-bit is high in e3 mode. this bit will not go active if losalm, oofalm, or aisdet are active. aisdet alarm indication signal detect ? set if there is valid framing and parity, all c-bits are 0, both x-bits are equal, and the payload contains a 1010... pattern starting with a one after each overhead bit in ds3 mode. this bit is set when an unframed all-ones signal is received in e3 mode. oofalm out of frame alarm ? set when any 3 out of 16 consecutive f framing bits are in error or when 2 out of 3 consecutive m frames have errors in the m bit positions in ds3 mode. this bit is set when four consecutive fas errors have been received in e3 mode. this condition will initiate a reframe. losalm loss-of-signal alarm ? indicates that the received signal prior to b3zs/hdb3 decoding has been low for 175 75 clock cycles. this indicates that the ds3/e3 line signal has been lost. this signal is set as soon as the loss-of-signal condition is detected and is cleared when at least 33 percent (25 percent in e3 mode) one's density is achieved for 175 75 clock cycles 7 6 5 4 3 2 1 0 refrm frmtid1 frmtid0 idledet yeldet aisdet oofalm losalm
cn8330 3.0 registers ds3/e3 framer with 52 mbps hdlc controller 3.2 status registers 100441e conexant 3-7 0x11?counter interrupt status register (sr01) the counter interrupt status register contains status information about active interrupts needing service from the controller. this register needs to be read by the controller upon receiving a counter interrupt to determine the source of the interrupt. the interrupt indications are active high in the register and are available even if they are not enabled to be visible on the cntint/linelb output pin. servicing will clear this interrupt indication as described in microprocessor interrupts in the microprocessor interface section in the functional description chapter. counter operation is discussed in ds3/e3 error counters in the status registers section of this chapter. note(s): rsvd bits in control registers must be set to zero. shdwitr shadow status register interrupt ? set if any of the bits in the shadow status register get set. this bit is cleared by reading the shadow status register [sr06;0x16]. lcvctritr lcv counter interrupt ? set high on an lcv error counter roll-over or saturation. the lcv counter interrupt enable bit [lcvctrie;cr02.5] determines the status of the counter. this bit is cleared when this status register is read. febectritr febe event counter interrupt ? set high if the febe event counter has either rolled over or is saturated. the febe event counter interrupt enable [febectrie;cr02.4] determines the status of the counter. this bit is cleared when this status register is read. pthctritr path parity error counter interrupt ? set high if the path parity error counter has either rolled over or is saturated. the parity error counter interrupt enable bit [pthctrie.cr02.3] determines the status of the counter. this bit is cleared when this status register is read. ferrctritr frame error counter interrupt ? set high when the frame error counter has either rolled over or is saturated. the frame error counter interrupt enable [ferrctrie;cr02.2] determines the status of the counter. this bit is cleared when this status register is read. dgrctritr disagreement counter interrupt ? set high if the disagreement counters have either rolled over or are saturated. the disagreement counter interrupt enable bit [dgrctrie;cr02.1] determines the status of the counter. this bit is cleared when this status register is read. parctritr parity error counter interrupt ? set high if the parity error counter has either rolled over or is saturated. the parity error counter interrupt enable bit [parctrie;cr02.0] determines the status of the counter. this bit is cleared when this status register is read. 7 6 5 4 3 2 1 0 rsvd shdwitr lcvctritr febectritr pthctritr ferrctritr dgrctritr parctrlltr
3.0 registers cn8330 3.2 status registers ds3/e3 framer with 52 mbps hdlc controller 3-8 conexant 100441e 0x12?data link interrupt status register (sr02) the data link interrupt status register contains information about active data link interrupts needing service from the controller. the controller determines the source of the data link interrupt by reading this register. the interrupt indications are active high and can be from four sources: transmit feac channel, receive feac channel, transmit terminal data link, and receive terminal data link. servicing an interrupt clears the indication in this register. note(s): rsvd bits in control registers must be set to zero. txtdlitr transmit terminal data link interrupt ? set high when the transmitter has latched the present set of controls in the terminal data link control register [cr01; 0x01] and is ready for a new set. writing the terminal data link control register clears this interrupt. rxtdlitr receive terminal data link interrupt ? set high by the receive data link circuitry. reading the terminal data link status register clears this interrupt. txfeacitr transmit feac channel interrupt ? set high indicating that the transmitter is ready for a new byte to be written to the transmit feac channel byte register. writing the transmit feac channel byte clears this interrupt. rxfeacitr receive feac channel interrupt ? set high when a feac message byte has been received and placed in the receive feac channel byte register. reading the receive feac channel byte register clears this interrupt. 0x13?receive feac channel byte (sr03) rxfeac[7:0] receive feac channel message byte ? if the incoming format is c-bit parity, this register contains the received byte from the bit-oriented receive feac channel. the receive feac channel is only defined in c-bit parity format. receive feac message reception is described in rxfeac channel reception in the receiver operation section of the functional description chapter. this byte is meaningless in e3 mode and should be ignored. 7 6 5 4 3 2 1 0 rsvd rsvd rsvd rsvd txtdlitr rxtdlitr txfeacitr rxfeacltr 7 6 5 4 3 2 1 0 rxfeac[7] rxfeac[6] rxfeac[5] rxfeac[4] rxfeac[3] rxfeac[2] rxfeac[1] rxfeac[0]
cn8330 3.0 registers ds3/e3 framer with 52 mbps hdlc controller 3.2 status registers 100441e conexant 3-9 0x14 ? terminal data link status register (sr04) the terminal data link status register contains the status indications for the lapd receiver of the terminal data link. this data link is only defined in c-bit parity or e3 modes. terminal data link reception is described in the receiver operation section of the functional description chapter. terminal data link receiver functions include fcs checking, transparency bit removal, and flag detection. lapd messages may be read from the receive terminal data link message buffer [rxtdl;0x40 ? 0x47], and require the use of the dlint/sourcelb interrupt to synchronize the transfer of message data between the receiver and microprocessor. note(s): reserved bits in control registers must be set to zero. rxbyte[2:0] byte pointer ? a 3-bit pointer to the last location written in the receive terminal data link message buffer. rxidle idle code received ? indicates that an idle flag sequence (01111110) was received on the terminal data link. badfcs bad fcs ? set when an erroneous fcs was received at the end of a message or an idle flag is received that is not byte aligned. rxabort abort flag received ? set if an abort sequence (seven consecutive ones) is received on the terminal data link. 0x15 ? part number/hardware version register (sr05) the part number/hardware version register contains a part number in the upper nibble and a version number in the lower nibble. this register is provided so that the processor will know what version of the cn8330 is present. this enables loading of version-specific software, if needed. the part number for the cn8330 framer is 0000. the version number is indicated below and will be incremented with any change in circuitry within the ic. u 7 6 5 4 3 2 1 0 reserved reserved rxbyte[2] rxbyte[1] rxbyte[0] rxidle badfcs rxabort 7 6 5 4 3 2 1 0 part[3] part[2] part[1] part[0] ver[3] ver[2] ver[1] ver[0] conexent part number obsolete base 2 part number hex value cn8330epj uga-330-1 0x01 cn8330epjb uga-330-2 0x02 cn8330epjc/cn8330epfc ? 0x03 cn8330epjd/cn8330epfd ? 0x04
3.0 registers cn8330 3.2 status registers ds3/e3 framer with 52 mbps hdlc controller 3-10 conexant 100441e 0x16 ? shadow status register (sr06) the shadow status register contains copies of the five least significant bits of the ds3/e3 maintenance status register [sr00;0x10]. whenever a status indication appears in the ds3/e3 maintenance status register, the corresponding bit is also set in the shadow status register. the bits in this shadow status register are latched and held until the controller reads the register. this register provides a way to monitor transient occurrences of alarm indications without continuously polling the ds3/e3 maintenance status register. an additional bit not contained in the ds3/e3 maintenance status register is all-ones detect . if the shadow interrupt is enabled, any occurrence of an indication in bits 0 through 4 will cause an active low interrupt to occur on the cntint/linelb pin. note(s): rsvd bits in control registers must be set to zero. shdwall1 shadow all-ones detect ? set whenever an unframed all-ones signal has been detected in either ds3 or e3 mode. shdwidle shadow idle code detect ? set if there is valid framing and parity, the three c-bits in subframe 3 are zero, both x-bits are equal, and the payload contains a 1100... pattern starting with a 11 after each overhead bit in ds3 mode. this bit will be low in e3 mode since there is no defined e3 idle signal. shdwyel shadow yellow alarm detect ? set for one m-frame interval when both x-bits are low in the previous m-frame in ds3 mode. this bit is set when the received a-bit is high in e3 mode. shdwais shadow alarm indication signal detect ? set if there is valid framing and parity, all c-bits are 0, both x-bits are equal, and the payload contains a 1010... pattern starting with a one after each overhead bit in ds3 mode. this bit is set when an unframed all-ones signal is received in e3 mode. shdwoof shadow out of frame ? set when any 3 out of 16 consecutive f framing bits are in error or when 2 out of 3 consecutive m-frames have errors in the m-bit positions in ds3 mode. this bit is set when four consecutive fas errors have been received in e3 mode. this condition will initiate a reframe. shdwlos shadow loss-of-signal alarm ? indicates that the received signal prior to b3zs/hdb3 decoding has been low for 175 75 clock cycles. this indicates that the cn8330 line signal has been lost. this signal is set as soon as the loss-of-signal condition is detected and is cleared when at least 33percent (25 percent in e3 mode) one's density is achieved for 175 75 clock cycles. 7 6 5 4 3 2 1 0 rsvd rsvd shdwall1 shdwidle shdwyel shdwais shdwoof shdwlos
cn8330 3.0 registers ds3/e3 framer with 52 mbps hdlc controller 3.2 status registers 100441e conexant 3-11 0x20 ? 0x26 ? ds3/e3 error counters there are six error counters for ds3/e3 errors located at addresses 0x20 ? 0x26. all are 8-bit counters with the exception of the ds3 disagreement [sr08;0x21] and ds3/e3 lcv counters [sr12,sr13;0x25,0x26]. the 8-bit counters indicate 0 through 255 counts of a particular error. if the interrupt for a particular counter is not enabled, the counter will saturate at 255 when more than 255 counts of that error are received and the saturation indication will appear in the counter interrupt status register [sr01;0x01]. the saturation indication and the counter will be cleared when the counter is read. if the interrupt for a particular counter is enabled in the interrupt control register [cr02; 0x02], then the counter will not saturate but will roll over and continue counting from zero. an interrupt will be generated on the cntint/linelb output pin and will appear in the counter interrupt status register when the counter rolls over to a count of zero. the interrupt will be cleared when the counter interrupt status register is read. the only valid counters in e3 mode are the ds3/e3 lcv and frame error counters. the ds3/e3 frame error counter [sr09;0x22] counts each occurrence of an incorrect pattern in the 10-bit fas. all counters are cleared when read by the microprocessor. the interrupt indication for a particular counter is also cleared when the counter is read. both nibbles of the ds3 disagreement counter [sr08;0x21] are cleared when address 0x21 is read. each byte of the ds3/e3 lcv counter is cleared separately when it is read. software should read the low byte first and then the high byte to prevent any missed counts. all counters are designed so that errors occurring during reads by the microprocessor will not be missed or double-counted. all counters except for lcv and frame error are frozen during an oof condition. the lcv and frame error counters continue counting errors during an oof condition. both counters also have ripple carry outputs available when the ppdl port is not in use. these outputs are on the rdat[5] and idle pins, respectively. saturation of these two counters can be disabled without enabling the respective interrupts by setting the disable saturation of lcv/frame errors bit [dislcv/ferr;cr04.4] in the feature control register [cr04;0x04]. this allows external enlargement of these counters by use of the ripple carry outputs without interruption of the microprocessor. 0x20 ? ds3 parity error counter (sr07) ds3parctr[7:0] ds3 parity error counter ? increments for each m-frame in which the calculated parity of the received data bits of the previous m-frame do not match the received parity bits. if the two parity bits are different this counter will increment. 7 6 5 4 3 2 1 0 ds3parctr[7] ds3parctr[6] ds3parctr[5] ds3parctr[4] ds3parctr[3] ds3parctr[2] ds3parctr[1] ds3parctr[0]
3.0 registers cn8330 3.2 status registers ds3/e3 framer with 52 mbps hdlc controller 3-12 conexant 100441e 0x21 ? ds3 disagreement counter (sr08) the ds3 disagreement counter consists of two 4-bit counters. both counters indicate 0 through 15 counts of disagreements in either the two x (yellow alarm) bits or the two p (parity) bits. if the interrupt is not enabled, the counters saturate at 15 when more than 15 counts are received. saturation of either 4-bit counter will generate a disagreement counter interrupt indication in counter interrupt status register [sr01;0x11]. if the disagreement interrupt is enabled, the counters will roll over and continue counting after 15 error counts and generate an interrupt in counter interrupt status register and on the cntint/linelb pin. pardgrctr[3:0] parity-bit disagreement counter ? if the two p-bits in an m-frame are in disagreement, the p-bit disagreement counter nibble will be incremented. xdgrctr[3:0] x-bit disagreement counter ? if the two x-bits in an m-frame are in disagreement (due to line errors), the x-bit disagreement counter nibble will be incremented. 0x22 ? ds3/e3 frame error counter (sr09) ferrctr[7:0] frame error counter ? increments with each error in the m- or f-bit framing pattern in ds3 mode and with each error in the fas pattern in e3 mode. errors are still counted during an oof condition (oofalm = 1). 0x23 ? ds3 path parity error counter (sr10) ds3pthctr[7:0] ds3 path parity error counter ? increments for each m-frame in which the calculated parity of the received data bits of the previous m-frame do not match a majority vote of the three received cp bits (c-bits in subframe 30). 7 6 5 4 3 2 1 0 pardgrctr[3] pardgrctr[2] pardgrctr[1] pardgrctr[0] xdgrctr[3] xdgrctr[2] xdgrctr[1] xdgrctr[0] 7 6 5 4 3 2 1 0 ferrctr[7] ferrctr[6] ferrctr[5] ferrctr[4] ferrctr[3] ferrctr[2] ferrctr[1] ferrctr[0] 7 6 5 4 3 2 1 0 ds3pthctr[7] ds3pthctr[6] ds3pthctr[5] ds3pthctr[4] ds3pthctr[3] ds3pthctr[2] ds3pthctr[1] ds3pthctr[0]
cn8330 3.0 registers ds3/e3 framer with 52 mbps hdlc controller 3.2 status registers 100441e conexant 3-13 0x24 ? ds3 febe event counter (sr11) ds3febe[7:0] ds3 febe event counter ? increments for each m-frame where any c-bit in subframe 4 is zero. 0x25,0x26 ? ds3/e3 lcv counter ? low and high bytes (sr12,sr13) the ds3/e3 lcv counter is a 16-bit counter with the low byte located at address 0x25 and the high byte located at address 0x26. if the interrupt for the ds3/e3 lcv counter is not enabled, the counter will saturate at 65535 and the saturation indication will appear in the counter interrupt status register [sr01;0x11]. if the interrupt is enabled, the counter will roll over and continue counting as for the 8-bit counters. in ds3 mode, this counter increments upon each occurrence of a bipolar violation (bpv) and each sequence of three or more zeroes. in e3 mode, it increments only upon each occurrence of an lcv per itu-t o.161 (an lcv is defined as two consecutive bpvs of the same polarity). 7 6 5 4 3 2 1 0 ds3febe[7] ds3febe[6] ds3febe[5] ds3febe[4] ds3febe[3] ds3febe[2] ds3febe[1] ds3febe[0] 7 6 5 4 3 2 1 0 lcvctr[7] lcvctr[6] lcvctr[5] lcvctr[4] lcvctr[3] lcvctr[2] lcvctr[1] lcvctr[0] 15 14 13 12 11 10 9 8 lcvctr[15] lcvctr[14] lcvctr[13] lcvctr[12] lcvctr[11] lcvctr[10] lcvctr[9] lcvctr[8]
3.0 registers cn8330 3.3 memory registers ds3/e3 framer with 52 mbps hdlc controller 3-14 conexant 100441e 3.3 memory registers 0x30 ? 0x37 ? transmit terminal data link message buffer (txtdl) the transmit terminal data link message buffer locations are loaded with the message bytes to be sent on the terminal data link in response to the transmit terminal data link interrupt. 0x40 ? 0x47 ? receive terminal data link message buffer (rxtdl) the receive terminal data link message buffer contains the message bytes received on the terminal data link. the receive terminal data link interrupt indicates the presence of data in the receive buffer. 7 6 5 4 3 2 1 0 txtdl[7] txtdl[6] txtdl[5] txtdl[4] txtdl[3] txtdl[2] txtdl[1] txtdl[0] 7 6 5 4 3 2 1 0 rxtdl[7] rxtdl[6] rxtdl[5] rxtdl[4] rxtdl[3] rxtdl[2] rxtdl[1] rxtdl[0]
cn8330 ds3/e3 framer with 52 mbps hdlc controller 3.4 register summary 100441e conexant 3-15 3.4 register summary table 3-1. register overview addr register label read write bit number 7 6 5 4 3 2 1 0 0x00 cr00 r/w linelp sourcelp txalm1 txalm0 extovh extcbit e3frm cbitp/dl 0x01 cr01 r/w rxtdlie distxtdl txbyte[2] txbyte[1] txbyte[0] txabort txfcs txmsg 0x02 cr02 r/w sr6ie rxfeacie lcvctrie febectrie pthctrie ferrctrie dgrctrie parctrie 0x03 cr03 r/w txfeac[7] txfeac[6] txfeac[5] txfeac[4] txfeac[3] txfeac[2] txfeac[1] txfeac[0] 0x04 cr04 r/w tsteqsel ami/lcv2 disenc dislcv/ferr paraen febec[3] febec[2] febec[1] 0x05 cr05 r/w fcscnt[3] fcscnt[2] fcscnt[1] fcscnt[0] limitfcs crc32 disppdl nibble table 3-2. status registers (1 of 2) addr register label read write bit number 7 6 5 4 3 2 1 0 0x10 sr00 r refrm fmtid1 fmtid0 idledet yeldet aisdet oofalm losalm 0x11 sr01 r rsvd shdwitr lcvctritr febectritr pthctritr ferrctritr dgrctritr parctritr 0x12 sr02 r rsvd rsvd rsvd rsvd txtdlitr rxtdlitr txfeacitr rxfeacitr 0x13 sr03 r rxfeac[7] rxfeac[6] rxfeac[5] rxfeac[4] rxfeac[3] rxfeac[2] rxfeac[1] rxfeac[0] 0x14 sr04 r rsvd rsvd rxbyte[2] rxbyte[1] rxbyte[0] rxidle badfcs rxabort 0x15 sr05 r part[3] part[2] part[1] part[0] ver[3] ver[2] ver[1] ver[0] 0x16 sr06 r rsvd rsvd shdwall1 shdwidle shdwyel shdwais shdwoof shdwlos 0x20 sr07 r ds3 parctr[7] ds3parctr[6] ds3parctr[5] ds3parctr[4] ds3parctr[3] ds3parctr[2] ds3parctr[1] ds3parctr[0] 3
cn8330 3.4 register summary ds3/e3 framer with 52 mbps hdlc controller 3-16 conexant 100441e 0x21 sr08 r pardgrctr[3] pardgrctr[2] pardgrctr[1] pardgrctr[0] xdgrctr[3] xdgrctr[2] xdgrctr[1] xdgrctr[0] 0x22 sr09 r ferrctr[7] ferrctr[6] ferrctr[5] ferrctr[4] ferrctr[3] ferrctr[2] ferrctr[1] ferrctr[0] 0x23 sr10 r ds3pthctr[7] ds3pthctr[6] ds3pthctr[5] ds3pthctr[4] ds3pthctr[3] ds3pthctr[2] ds3pthctr[1] ds3pthctr[0] 0x24 sr11 r ds3febe[7] ds3febe[6] ds3febe[5] ds3febe[4] ds3febe[3] ds3febe[2] ds3febe[1] ds3febe[0] 0x25 sr12 r lcvctr[7] lcvctr[6] lcvctr[5] lcvctr[4] lcvctr[3] lcvctr[2] lcvctr[1] lcvctr[0] 0x26 sr13 r lcvctr[15] lcvctr[14] lcvctr[13] lcvctr[12] lcvctr[11] lcvctr[10] lcvctr[9] lcvctr[8] table 3-3. transmit terminal data link message buffer addr register label read write bit number 7 6 5 4 3 2 1 0 0x30 ? 0x37 txtdl r/w txtdl[7] txtdl[6] txtdl[5] txtdl[4] txtdl[3] txtdl[2] txtdl[1] txtdl[0] table 3-4. receive terminal data link message buffer addr register label read write bit number 7 6 5 4 3 2 1 0 0x40 ? 0x47 rxtdl r/w rxtdl[7] rxtdl[6] rxtdl[5] rxtdl[4] rxtdl[3] rxtdl[2] rxtdl[1] rxtdl[0] table 3-2. status registers (2 of 2) addr register label read write bit number 7 6 5 4 3 2 1 0
100441e conexant 4-1 4 4.0 mechanical/electrical specifications 4.1 timing requirements table 4-1 and figure 4-1 illustrate the timing requirements for the microprocessor interface. the parameter t cyc is the period of the receive ds3/e3 clock (ds3cki). this clock signal is used in the read circuit of the microprocessor to ensuring no status events are missed and that counter values are accurately read. read operation requires the read strobe to be low for three t cyc clock cycles ensuring that changing status and error counts are properly processed. if a gapped clock is applied to the circuit, it is sufficient to allow three receive clock cycles between read strobes to allow a latching circuit to clear in the microprocessor interface. table 4-1. microprocessor interface timing (1 of 2) symbol parameter min. typical max. units t as address setup before ale low 7 ?? ns t cale controller ale pulse width 34 ?? ns t ah address hold after ale low 10 ?? ns t rwa rd*/wr* high to ale high 10 ?? ns t adwrh address/select to wr* high 117 ?? ns t adrdl address/select to rd* low 17 ?? ns t wrw (read operation) rd* pulse width (1) 3 t cyc ?? ns t wrw (write operation) wr* pulse width 100 ?? ns t rdd rd* low to data available ?? 30 ns t rdh read data hold time (2) 3 ?? ns
4.0 mechanical/electrical specifications cn8330 4.1 timing requirements ds3/e3 framer with 52 mbps hdlc controller 4-2 conexant 100441e t clcl ale low to rd*/wr* low 10 ?? ns t ds data stable before wr* high 25 ?? ns t dh data hold after wr* high 10 ?? ns t sh address/select hold after rd*/wr* low 110 ?? ns ? controller port cycle time 154 ?? ns note(s): (1) t cyc = period of clock connected to the ds3cki pin. (2) the external address/data bus capacitance will increase the data hold time if the bus remains undriven. table 4-1. microprocessor interface timing (2 of 2) symbol parameter min. typical max. units figure 4-1. microprocessor interface timing t adrdl t adwrh t wrw t sh t rdd t ds t dh t rdh t rwa t as t ah t clcl t cale cs rd*/wr* ad[7:0] ale
cn8330 4.0 mechanical/electrical specifications ds3/e3 framer with 52 mbps hdlc controller 4.1 timing requirements 100441e conexant 4-3 figure 4-2 and tables 4-2 through table 4-4 illustrate the clock and data relationships for all output and input signals. propagation delays for the output signals are listed below. the output signal timings are relative to the listed edge of the clock. clock outputs derived from clock inputs are listed with the edge as both. this means that the delay number given applies for either edge. input signals should have setup and hold times with respect to the listed edge of the given input clock. all times are listed in nanoseconds and are measured with 30 pf loading on the output pins. table 4-2. clock timing requirements timing requirements clock min. typical (44.736 mhz) typical (34.368 mhz) units low pulse width - wl rxcki, ds3cki, txcki 5.0 11.2 14.55 ns high pulse width - wh rxcki, ds3cki, txcki 5.0 11.2 14.55 ns cycle time - t cyc rxcki, ds3cki, txcki 19.0 22.4 29.1 ns cycle time ?? 8 rxcki ns low pulse width rxbck 6 rxcki ?? ns high pulse width rxbck 2 rxcki ?? ns figure 4-2. output and input signal timing t pd clock output signal input signal input clock p wl p wh t su t hd
4.0 mechanical/electrical specifications cn8330 4.1 timing requirements ds3/e3 framer with 52 mbps hdlc controller 4-4 conexant 100441e table 4-3. output signal timing output symbol clock t pd min t pd max edge units rxclk ds3cki/rxcki 2.8 13.0 rising ns rxmsy rxclk 1.8 5.0 rising ns rxdat rxclk 1.6 5.2 rising ns rxcck rxclk 3.2 9.1 rising ns cbito rxcck t cyc +1.0 t cyc +2.0 rising ns rxovh rxclk 2.5 11.1 rising ns rxbck rxclk 2.0 10.0 falling ns rxgapck ds3cki/rxcki 2.8 22.0 both ns rxgapck rxclk 1.0 9.0 both ns rdat[7] /txnrz tclko 1.2 7.0 rising ns txpos/txneg tclko 1.2 8.2 rising ns txsyo txcki 3.2 11.1 rising ns txgapck txcki 2.2 11.7 both ns txbck txcki 3.0 16.0 rising ns tclko txcki 2.8 12.8 rising ns txovh txcki 3.4 15.6 falling ns table 4-4. input setup/hold timing input symbol clock t su min t hld min edge units cbiti txcck 2 t cyc 4 t cyc falling ns tdat[7:0] (parallel mode) txbck ? 2 t cyc full txbck period rising ns sndmsg,sndfcs txbck ? 2 t cyc full txbck period rising ns txsyi txcki 1.0 6.0 rising ns txdati txcki 1.0 6.0 falling ns txeni tclko 9.0 0.0 rising ns lcverri tclko 9.0 0.0 rising ns rxpos, rxneg ds3cki 1.0 5.0 rising ns
cn8330 4.0 mechanical/electrical specifications ds3/e3 framer with 52 mbps hdlc controller 4.2 environmental conditions 100441e conexant 4-5 4.2 environmental conditions 4.2.1 power requirements and temperature range stresses above those listed as absolute maximum ratings (see table 4-5 ) may cause permanent damage to the device. this is a stress rating only, and functional operation of the device at these or any other conditions above those indicated in the other sections of this document is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. table 4-5. absolute maximum ratings parameter symbol value unit supply voltage v dd ? 0.3 to +7.0 volts input voltage v in ? 0 to v dd +0.3 volts output voltage v out ? 0.3 to v dd +0.3 volts operating temperature t a ? 40 to +85 c storage temperature t stg ? 55 to +150 c operating supply voltage v dd +4.75 to +5.25 volts thermal impedance ja 68 plcb ? thermal impedance ja 80 tofp ?
4.0 mechanical/electrical specifications cn8330 4.3 electrical characteristics ds3/e3 framer with 52 mbps hdlc controller 4-6 conexant 100441e 4.3 electrical characteristics 4.3.1 dc characteristics all inputs and bidirectional signals have input thresholds compatible with ttl drive levels. all outputs are cmos drive levels and can be used with cmos or ttl logic (see table 4-6 and table 4-7 ). specific characteristics given in table 4-6 and table 4-7 apply over an operating temperature range of ? 40 to +85 c and a supply voltage range of 4.75 to 5.25 volts, unless otherwise noted. table 4-6. dc characteristics parameter description conditions min typ max units v dd supply voltage ? 4.75 5.00 5.25 v v oh all outputs, except as noted in table 4-7 i oh = ? 4 ma 2.4 4.5 ? v v ol all outputs, except as noted in table 4-7 i ol = 4 ma ? 0.2 0.4 v v ih (1) input voltage high ? 2.0 ?? v v il input voltage low ??? 0.8 v i dd supply current v dd = 5.25 v @ 52 mhz ?? 175 ma i dd supply current v dd = 5.25 v @ 45 mhz ?? 150 ma i il input leakage current ?? 1.0 10 a c in input capacitance inputs and ad[7:0] ?? 3pf c out output capacitance all outputs ?? 10 pf ? esd protection mil-std-883c method 3015 2>3 ? kv ? latch-up input current jedec jc-40.2 150 >400 ? ma note(s): (1) following pins need slightly higher vih input voltage than specified: txcki = 2.2v, init_n = 2.1 v
cn8330 4.0 mechanical/electrical specifications ds3/e3 framer with 52 mbps hdlc controller 4.3 electrical characteristics 100441e conexant 4-7 table 4-7. output drive capability output pin drive current @ v oh or v ol rxclk 22 + 8 ma idle 24 + 2 ma valfcs 25 + 8 ma rdat[5, 3, 2, 1, 0] 32, 30, 29, 28, 27 + 2 ma cbito 37 + 2 ma rxcck 38 + 2 ma testo 41 + 2 ma txcck 46 + 2 ma txbck 57 + 8 ma cntint 62 + 2 ma dlint 63 + 2 ma
4.0 mechanical/electrical specifications cn8330 4.4 mechanical specifications ds3/e3 framer with 52 mbps hdlc controller 4-8 conexant 100441e 4.4 mechanical specifications figure 4-3. 68?pin plastic leaded chip carrier (j-bend) see detail 'a' .050" bsc. .025"/.045" r .026" .032" .013" .021" .042" .056" .020" min. d d 1 a a 1 ee 1 d 2 e 2 .042" .048" x 45? pin 1 identifier d 3 e 3 d 2 e 2 detail "a" inches millimeters s y m b o l a a 1 d d 1 d 2 d 3 e e 1 e 2 e 3 min. .165 .090 .985 .950 .445 .985 .950 .445 max. .200 .130 .995 .958 .465 .995 .958 .465 min. 4.20 2.29 25.02 24.13 11.30 25.02 24.13 11.30 max. 5.08 3.30 25.27 24.33 11.81 25.27 24.33 11.81 nom. nom. .800 ref. 20.32 ref. .800 ref. 20.32 ref. 68 plcc
cn8330 4.0 mechanical/electrical specifications ds3/e3 framer with 52 mbps hdlc controller 4.4 mechanical specifications 100441e conexant 4-9 figure 4-4. 80-pin metric quad flat pack (mqfp) s y m b o l all dimensions in millimeters min. nom. max. a a1 a2 d d1 d3 zd e e1 e3 ze l e b 2.20 ---- 1.95 17.05 13.95 ---- 17.05 13.95 ---- .70 ---- 2.25 0.25 2.0 17.20 14.00 12.35 0.825 17.20 14.00 12.35 0.825 .80 .65 .33 2.30 ---- 2.05 17.35 14.05 ---- 17.35 14.05 ---- .90 ----
4.0 mechanical/electrical specifications cn8330 4.4 mechanical specifications ds3/e3 framer with 52 mbps hdlc controller 4-10 conexant 100441e
100441e conexant a-1 a appendix a multimegabit hdlc formatter a.1 introduction the cn8330 was designed as a ds3/e3 framer with both serial and parallel data inputs. the circuit has an integral high-level data link control (hdlc) interface that can be used without the insertion of ds3/e3 overhead bits. this mode of operation is documented in this appendix. the transmitter is capable of formatting byte-organized data from the payload parallel data link (ppdl) data port. the parallel data is formatted with idle flags, zero stuffing for transparency, and a selectable 16- or 32-bit frame check sequence (fcs) according to itu-t standard q.921 or iso 3309-1984. options are provided to allow the formatting of data for packet voice according to ansi standard t1.312-1991. serial data can be transmitted at any rate up to 52 mbps.
appendix a multimegabit hdlc formatter cn8330 a.1 introduction ds3/e3 framer with 52 mbps hdlc controller a-2 conexant 100441e the receiver provides complementary operation, deriving byte-organized data and hdlc protocol status including fcs checking at serial rates up to 52 mbps. figure a-1 illustrates the major data paths of the hdlc formatter. figure a-1. hdlc formatter block diagram microprocessor interface hdlc transmit transmit byte clock transmit data byte send message send fcs 8 fcs mode transmit clock in m u x line loopback data receive clock receive data off on transmit clock transmit data address/data control 8 loopbacks fcs mode transmit data transmit clock receive data receive clock 8 clock m u x data on off hdlc receive receive byte clock receive data byte idle status fcs status 8 fcs mode source loopback
cn8330 appendix a multimegabit hdlc formatter ds3/e3 framer with 52 mbps hdlc controller a.2 block and logic diagrams 100441e conexant a-3 a.2 block and logic diagrams the transmit serial clock is applied to the txcki input of the hdlc transmitter. the circuit generates a byte clock and either idle code, a serialized message byte, an fcs sequence, or an abort sequence on the rxcck/txnrz output pin in response to control signal inputs. at the end of a message, the fcs is generated. either a 16- or 32-bit cycle redundancy check (crc) can be generated for the fcs. a line loopback function that will loop the receive input directly to the transmit output for end-to-end loopback is provided. in the receive direction, serial data is taken from the receiver inputs rxpos and rxneg, or, if source loopback is set, from the transmitter output. the serial clock is connected to the ds3cki pin on the hdlc receiver. the receiver derives bytes of data, a byte clock, idle channel, and valid fcs indications from the received serial data. the source loopback function can be used to provide a diagnostic test of the hdlc transmitter and receiver. a microprocessor interface is required to configure the circuit for hdlc operation and to control loopbacks and fcs options for the hdlc transmitter and receiver. the control pins consist of the read and write strobes and a chip select signal.
appendix a multimegabit hdlc formatter cn8330 a.2 block and logic diagrams ds3/e3 framer with 52 mbps hdlc controller a-4 conexant 100441e figure a-2 is a logic diagram showing the functional partitioning of the pins. this diagram pertains only to hdlc mode operation, for which some of the pins are reassigned from cn8330 framer functions, i.e., the transmit data output comes from a pin (rxcck/txnrz) assigned to the receiver in cn8330 framer operation. figure a-2. hdlc formatter logic diagram 58 45 47 ? 50, 53 ? 56 43 42 rxdat rxmsy rxclk cbito txnrz rdat[7:0] idle valfcs vco rxbck txbck txcck txpos txneg txsyo tclko i = input, o = output receiver section transmitter section rxpos rxneg ds3cki rxcki fifen receive serial data output no connect receive clock output no connect transmit data output receive byte output receive idle status receive fcs status no connect receive byte clock transmit byte clock no connect no connect no connect no connect transmit clock output o o o o o o o o o o o o o o o o cntint dlint o o local processor interface txcki cbiti tdat[7:0] sndfcs sndmsg ale cs rd* wr* ad[7:0] ppdlonly mon/mic* testi init* receive data input receive data input receive clock input ground ground i i i i i i i i i i transmit clock input ground transmit byte input send fcs control send message control i i i i i/o address latch enable chip select read strobe write strobe address-data bus i i i i vcc ground ground initialization input no connect no connect testo o no connect control and test 13 14 15 16 11 20 21 22 37 38 34-22 24 25 12 23 67 64 65 66 2 ? 9 44 61 60 19 57 46 40 39 59 18 62 63 41
cn8330 appendix a multimegabit hdlc formatter ds3/e3 framer with 52 mbps hdlc controller a.2 block and logic diagrams 100441e conexant a-5 figure a-3. hdlc formatter logic diagram - 80-pin mqfp 56 42 44-47, 51-54 39 38 rxdat rxmsy rxclk cbito txnrz rdat[7:0] idle valfcs vco rxbck txbck txcck txpos txneg txsyo tclko i = input, o = output receiver section transmitter section rxpos rxneg ds3cki rxcki fifen receive serial data output no connect receive clock output no connect transmit data output receive byte output receive idle status receive fcs status no connect receive byte clock transmit byte clock no connect no connect no connect no connect transmit clock output o o o o o o o o o o o o o o o o cntint dlint o o local processor interface txcki cbiti tdat[7:0] sndfcs sndmsg ale cs rd* wr* ad[7:0] ppdlonly mon/mic* testi init* receive data input receive data input receive clock input ground ground i i i i i i i i i i transmit clock input ground transmit byte input send fcs control send message control i i i i i/o address latch enable chip select read strobe write strobe address-data bus i i i i vcc ground ground initialization input no connect no connect testo o no connect control and test 5 6 7 8 3 12 13 14 33 34 22-29 16 17 4 15 69 66 67 68 73-80 41 63 58 11 55 43 36 35 57 10 64 65 37
appendix a multimegabit hdlc formatter cn8330 a.3 ppdl transmitter ds3/e3 framer with 52 mbps hdlc controller a-6 conexant 100441e a.3 ppdl transmitter the ppdl transmitter is enabled by setting the parallel data enable bit [paraen; cr04.3] in the feature control register [cr04;0x04]. the ppdl formatter is controlled by signals applied on the sndmsg and sndfcs pins. byte-wide data is provided on the tdat[7:0]. optional hdlc formatting with 16-bit or 32-bit fcss are provided. transmitter operation is controlled by the sndmsg and sndfcs pins. if no message is in progress (sndmsg and sndfcs both low), idle flags (01111110) are continuously transmitted in the data stream. setting sndmsg high initiates message transmission. data bytes and control signals are provided in response to the rising edge of the transmit byte clock txbck and are sampled internally after the falling edge. the data and controls should be held for a full period of txbck. the least significant bit of the transmitted bytes is applied to tdat[0] and the most significant to tdat[7]; transmission is least significant bit first. the transmitter performs automatic zero stuffing for transparency and fcs calculation for the data. the message must be an integral number of bytes in length. the fcs is 16 or 32 bits in length depending on the setting of the 32-bit crc select control bit [crc32;cr05.2] in the ppdl control register [cr05;0x05]. if this bit is low, the fcs is calculated with the polynomial: x 16 +x 12 +x 5 +1. if a 32-bit crc is selected by setting the crc32 high, then sndfcs shown in figure a-4 must be high for 4 cycles of the transmit byte clock and the fcs is calculated with the polynomial: x 32 +x 26 +x 23 +x 22 +x 16 +x 12 +x 11 +x 10 +x 8 +x 7 +x 5 +x 4 +x 2 +x+1 the fcs is transmitted by setting both the sndmsg and sndfcs pins high after the last data byte has been transmitted. sndfcs should be high for 2 byte clocks in 16-bit fcs mode and for 4 byte clocks in 32-bit fcs mode. an abort sequence may be transmitted by setting sndfcs high while sndmsg is set low. timing for the transmit operation is shown in figure a-4. figure a-4. ppdl transmitter timing txcki sndmsg txbck tdat[7:0] sndfcs data data
cn8330 appendix a multimegabit hdlc formatter ds3/e3 framer with 52 mbps hdlc controller a.3 ppdl transmitter 100441e conexant a-7 the transmit byte clock (txbck) is generated from the transmit clock input (txcki) and has a duty cycle of 25 percent. txbck will nominally be one-eighth of the txcki frequency but is influenced by hdlc transparency bit insertions. in the absence of any transparency bit insertions, there will be one pulse on txbck for every eight clock cycles of the txcki input. when a transparency bit is inserted into the serial transmit data stream, the txbck period will be lengthened to nine clock cycles of txcki (or 10 clock cycles if two transparency bit insertions occur within the same octet interval). txbck is present continuously even during the transmission of idle flags. the actual setup times on tdat[7:0], sndmsg, and sndfcs relative to the rising edge of txbck are negative. therefore, it is possible to read data and control from a ram or fifo buffer with the rising edge. cn8330 will sample the data after the falling edge. this allows fifos or rams with access times of 35 ? 40 ns to be used. fcs calculation can be limited to the first n bytes of the transmitted message by setting the limit frame check sequence calculation [limitfcs;cr05.3] control bit. in this mode, the fcs is calculated on the first n bytes transmitted after the opening flag and then held until the end of the message. it is then appended to the end of the message in normal fashion. the desired number n can be from 1 to 16 (a value of 0 gives n = 16) and is loaded in the frame check sequence calculation count[3:0] [fcscnt;cr05.7:4] control field. this allows fcs calculation only on the header information in a t1 packet voice format. a.3.1 ppdl receiver the ppdl receiver circuitry is activated when the paraen bit in the feature control register is set. the receiver performs idle flag detection, stuffed zero deletion, and fcs checking on the incoming data stream. the recovered data bytes are presented on rdat[7:0] and are valid on both the rising and falling edges of rxbck; the least significant bit is on rdat[0] and the most significant bit is on rdat[7]; the least significant bit is the first received from the serial input. if the payload stream contains idle flags, the idle pin will be high and the flags will be present on rdat[7:0]. if a valid fcs is received at the end of the message block, then the valfcs pin will be active high while idle is high. at the start of the next message, both indications will go low until the end of the incoming message has been received. if a bad fcs is received, idle will go high and valfcs will remain low. if valfcs goes high and idle does not, an abort sequence was received in the data. if there is only one flag received between incoming packets, there will be only one rxbck pulse present while idle is high. if crc 32-bit is low, the fcs is checked with the polynomial: x 16 +x 12 +x 5 +1 if a 32-bit crc is selected by setting crc32 bit high, then the fcs is checked with the polynomial: x 32 +x 26 +x 23 +x 22 +x 16 +x 12 +x 11 +x 10 +x 8 +x 7 +x 5 +x 4 +x 2 +x+1
appendix a multimegabit hdlc formatter cn8330 a.3 ppdl transmitter ds3/e3 framer with 52 mbps hdlc controller a-8 conexant 100441e timing for this operation is shown in figure a-5 . shown are cases of a good packet received, a packet received with a bad fcs, and an aborted packet. each packet is shown with one idle flag marking the end of the packet and the start of the next packet. however, more than one flag can occur in the serial stream. the output data will contain each occurrence of idle or abort flags with a pulse on rxbck. the receive byte clock rxbck is generated from the falling edge of the receive serial clock input on ds3cki and is present continuously like the transmit byte clock. nominally there will be one pulse on rxbck for every eight clock cycles on the receive serial clock. when an inserted transparency bit must be deleted, the rxbck period will be lengthened by one serial clock cycle. rxbck is present during the reception of fcs octets and idle flags. on a received message with a valid 16-bit fcs, the last 2 byte clocks prior to idle and valfcs going high will be the received fcs octets that were appended to the end of the message by the transmitter. in 32-bit mode, the last four received octets will be fcs octets. the rdat[7:0], idle, and valfcs outputs are valid at least one serial clock cycle period before the rising edge of rxbck and are valid for at least two serial clock cycle periods after the falling edge of rxbck. fcs checking can be limited to the first n bytes of the received message by setting the limitfcs control bit. in this mode, the fcs is checked only on the first n bytes received after the opening flag and then held until the end of the message. the locally calculated fcs is then compared to the last 2/4 bytes in the message to determine if a valid fcs was received. the desired number n can be from 1 to 16 (a value of 0 gives n=16) and is loaded in the fcscnt control field. this allows fcs checking only on the header information in a t1 packet voice format.
cn8330 appendix a multimegabit hdlc formatter ds3/e3 framer with 52 mbps hdlc controller a.3 ppdl transmitter 100441e conexant a-9 figure a-5. ppdl receiver timing rxclk idle aborted packet rxbck rdat[7:0] valfcs abort data data flag valfcs idle packet w/bad fcs valfcs idle good packet rdat[7:0] data fcs flag data fcs data
appendix a multimegabit hdlc formatter cn8330 control registers ds3/e3 framer with 52 mbps hdlc controller a-10 conexant 100441e control registers 0x00 ? mode control register (cr00) note: rsvd bits in control registers must be set to zero. linelp line loopback enable ? set to enable the loopback in the external direction. this loopback connects the received data stream before b3zs/hdb3 decoding to the transmitter outputs. the received data is still presented to all receiver blocks and is present on the receiver output pins. sourcelp source loopback enable ? set to enable the loopback in the internal direction. this loopback connects the encoded transmitter data and clock directly to the receiver. transmission of data on the line is not affected by this loopback. 0x04 ? feature control register (cr04) the feature control register is provided to enable or disable miscellaneous features in the cn8330 framer. note: rsvd bits in control registers must be set to zero. paraen parallel data enable ? set high to enable the ppdl transmitter and receiver as the source and sink for data. eight-bit data bytes are provided on the tdat[7:0] and rdat[7:0] buses for the ppdl transmitter and receiver. this bit must be set to 1 for operation as an hdlc formatter. 7 6 5 4 3 2 1 0 linelp sourcelp rsvd rsvd rsvd rsvd rsvd rsvd 7 6 5 4 3 2 1 0 rsvd rsvd rsvd rsvd paraen rsvd rsvd rsvd
cn8330 appendix a multimegabit hdlc formatter ds3/e3 framer with 52 mbps hdlc controller control registers 100441e conexant a-11 0x05 ? ppdl control register (cro5) the ppdl control register is provided to control the mode of operation of the ppdl transmitter and receiver. note: rsvd bits in control registers must be set to zero. fcscnt[3:0] fcs calculation count ? determines the number of bytes over which the fcs is to be calcu- lated. the number of bytes for calculation can be from 1 to 16 (a value of zero defaults to 16 bytes of calculation). limitfcs limit fcs calculation ? set to enable fcs calculation only on the first n bytes of an hdlc frame where n is determined by the fcs calculate count field. if this bit is low, the fcs will be calculated over all transmitted bytes. crc32 32-bit crc select ? set high to enable 32-bit crc generation and checking on the ppdl. if this bit is low, then 16-bit crc generation and checking is enabled. 7 6 5 4 3 2 1 0 fcscnt[3] fcscnt[2] fcscnt[1] fcscnt[0] limitfcs crc32 rsvd rsvd
appendix a multimegabit hdlc formatter cn8330 control registers ds3/e3 framer with 52 mbps hdlc controller a-12 conexant 100441e
100441e conexant b-1 b appendix b this appendix describes the various non-conformances associated with this device. b.1 ds3cki clock duty cycle conexant recommends a 60/40 percent duty cycle maximum for the ds3cki input. b.2 overhead bit insertion in e3 parallel payload mode when the framer is operated in e3 parallel payload mode with external overhead insertion enabled, the receive byte clock does not provide pulses where the overhead bits are inserted. workaround: an external hardware circuit can be constructed to provide a continuous byte clock synchronous to the receive byte clock. contact the conexant applications department for circuit details.
appendix b cn8330 b.3 hdlc formatter mode support while configured for e3 framing ds3/e3 framer with 52 mbps hdlc controller b-2 conexant 100441e b.3 hdlc formatter mode support while configured for e3 framing this mode was previously selected by configuring the following bits: cr00.3=1 (e3frm), cr04.3 (paraen) and cr05.1=0 (disppdl).if this mode is selected, the zero insertion function of the hdlc formatter incorrectly inserts an extra zero when the transmitted hdlc packet contains stuffed zeros that overlap the 16-bit e3 overhead. this transmitter malfunction causes the hdlc receiver to interpret the extra zero as data which results in an fcs errored packet. this problem prevents any customer from developing an e3 framed hdlc mode application. notice that parallel data still functions properly in e3 mode if cr05.1=1 (disppdl). workaround: by using two cn8330 devices with one operating in hdlc formatter mode and another device exclusively in e3 mode same results can be achieved.
100441e conexant c-1 c appendix c here's what we've recommended as a starting point for those customers who need a jitter attenuation pll for tbr24 compliance in e3 mode. an external jitter attenuation pll can be implemented for cn8330 with one vcxo and a passive lpf (low pass filter). the vco output from cn8330 is passed through the lpf to create a control voltage input to the vcxo. the vcxo output then connects to rxcki (and optionally to txcki) input of cn8330. the lpf circuit is shown below with the rc time constants used to establish the filter's cutoff frequencies as follows: t1 = r1 x c2 t2 = r2 x c2 t3 = r2 x c1 r and c values shown above are calculated for typical applications. vcxo specifications: t3 e3 units center frequency: 44.736 34.368 mhz frequency accuracy: +/- 20 +/- 20 ppm frequency pullability: +/- 200 +/- 200 ppm note: +/- 100 ppm frequency pullability may be adequate. 8330_001 from vco output to vcxo control input r1 c1 r2 c2 1 m 1 m 10 nf 100 nf gnd (analog)
appendix c cn8330 ds3/e3 framer with 52 mbps hdlc controller c-2 conexant 100441e the overall jitter transfer function also depends on the vcxo control voltage/frequency conversion ratio (ko) parameter measured in radians per second per volt. in our pll loop filter calculations, ko equals approximately 400 for a vcxo with +/- 200 ppm pullability. given ko, a 10hz break frequency is calculated for r1=r2=500k. with a 10hz break, attenuation at 100hz is around -12db, barely sufficient to meet 0.4ui output jitter required with 1.5ui input and 0.08ui intrinsic jitter. for added margin, r1=r2=1m puts the break frequency at 7hz. several cn8330 customers have tested the jitter attenuation pll with successfull results using r1=r2=1m. while this lpf should work for both t3 and e3 applications, we have not tested the pll to comply with any regulatory or interface requirements. lpf cutoff frequencies might have to be scaled to match desired loop timing characteristics or to have the desired cutoff frequency. we recommend all customers conduct performance evaluation and characterization testing of the pll before sending equipment for certification.
further information literature@c onexant.com 1-800-854-8099 (north america) 33-14-906-3980 (international) web site www.conexant.com world headquarters conexant systems, inc. 4311 jamboree road p. o. box c newport beach, ca 92658-8902 phone: (949) 483-4600 fax: (949) 483-6375 u.s. florida/south america phone: (727) 799-8406 fax: (727) 799-8306 u.s. los angeles phone: (805) 376-0559 fax: (805) 376-8180 u.s. mid-atlantic phone: (215) 244-6784 fax: (215) 244-9292 u.s. north central phone: (630) 773-3454 fax: (630) 773-3907 u.s. northeast phone: (978) 692-7660 fax: (978) 692-8185 u.s. northwest/pacific west phone: (408) 249-9696 fax: (408) 249-7113 u . s. south central phone: (972) 733-0723 fax: (972) 407-0639 u.s. southeast phone: (919) 858-9110 fax: (919) 858-8669 u.s. southwest phone: (949) 483-9119 fax: (949) 483-9090 apac headquarters conexant systems singapore, pte. ltd. 1 kim seng promenade great world city #09-01 east tower singapore 237994 phone: (65) 737 7355 fax: (65) 737 9077 australia phone: (61 2) 9869 4088 fax: (61 2) 9869 4077 china phone: (86 2) 6361 2515 fax: (86 2) 6361 2516 hong kong phone: (852) 2827 0181 fax: (852) 2827 6488 india phone: (91 11) 692 4780 fax: (91 11) 692 4712 korea phone: (82 2) 565 2880 fax: (82 2) 565 1440 phone: (82 53) 745 2880 fax: (82 53) 745 1440 europe headquarters conexant systems france les taissounieres b1 1681 route des dolines bp 283 06905 sophia antipolis cedex france phone: (33 1) 41 44 36 50 fax:(334)93003303 europe central phone: (49 89) 829 1320 fax: (49 89) 834 2734 europe mediterranean phone: (39 02) 9317 9911 fax: (39 02) 9317 9913 europe north phone: (44 1344) 486 444 fax: (44 1344) 486 555 europe south phone: (33 1) 41 44 36 50 fax:(331)41443690 middle east headquarters conexant systems commercial (israel) ltd. p. o. box 12660 herzlia 46733, israel phone: (972 9) 952 4064 fax: (972 9) 951 3924 japan headquarters conexant systems japan co., ltd. shimomoto building 1-46-3 hatsudai, shibuya-ku, tokyo 151-0061 japan phone: (81 3) 5371-1567 fax: (81 3) 5371-1501 taiwan headquarters conexant systems, taiwan co., ltd. room 2808 international trade building 333 keelung road, section 1 taipei 110, taiwan, roc phone: (886 2) 2720 0282 fax: (886 2) 2757 6760 0.0 sales offices

▲Up To Search▲

Price & Availability of 28330-DSH-002-A

	To Download 28330-DSH-002-A Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .